<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Uber</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Uber feed</description>
    <item>
      <title>How Uber Builds Zone-Failure-Resilient OpenSearch Clusters</title>
      <link>https://www.infoq.com/news/2026/07/uber-opensearch-zone-failure/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Uber</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/07/uber-opensearch-zone-failure/en/headerimage/generatedHeaderImage-1784274349171.jpg"/&gt;&lt;p&gt;Uber explained how it keeps its OpenSearch deployments running during a zone outage. It does this by using OpenSearch's built-in shard allocation and its own isolation-group system, which relies on the Odin container orchestration platform. This way, it maintains both query and ingestion capabilities.&lt;/p&gt; &lt;i&gt;By Claudio Masolo&lt;/i&gt;</description>
      <category>Uber</category>
      <category>OpenSearch</category>
      <category>Architecture</category>
      <category>Reliability</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 17 Jul 2026 10:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/07/uber-opensearch-zone-failure/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Uber</guid>
      <dc:creator>Claudio Masolo</dc:creator>
      <dc:date>2026-07-17T10:00:00Z</dc:date>
      <dc:identifier>/news/2026/07/uber-opensearch-zone-failure/en</dc:identifier>
    </item>
  </channel>
</rss>
