<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Availability - News</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Availability News feed</description>
    <item>
      <title>Meta’s ZGateway Cuts ZippyDB Connections 19x While Handling 1B+ Operations per Second</title>
      <link>https://www.infoq.com/news/2026/09/meta-zgateway-zippydb-proxy/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Availability-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/09/meta-zgateway-zippydb-proxy/en/headerimage/generatedHeaderImage-1789253966189.jpg"/&gt;&lt;p&gt;Meta has introduced ZGateway, a stateless proxy for ZippyDB that centralizes connection management, traffic routing, caching, load balancing, and admission control. The gateway handles more than 1 billion operations per second and about 40% of ZippyDB traffic, while Meta’s model estimates a 19x reduction in persistent connections.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Routing</category>
      <category>Scalability</category>
      <category>Database</category>
      <category>multi-region</category>
      <category>Caching</category>
      <category>Load Balancing</category>
      <category>Service Mesh</category>
      <category>Key-Value Store</category>
      <category>Availability</category>
      <category>Distributed Systems</category>
      <category>Fault Tolerance</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Mon, 28 Sep 2026 13:55:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/meta-zgateway-zippydb-proxy/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Availability-news</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-09-28T13:55:00Z</dc:date>
      <dc:identifier>/news/2026/09/meta-zgateway-zippydb-proxy/en</dc:identifier>
    </item>
    <item>
      <title>Uber Redesigns M3DB Sharding with Subclusters to Limit Failure Impact</title>
      <link>https://www.infoq.com/news/2026/09/uber-m3db-subcluster-sharding/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Availability-news</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/09/uber-m3db-subcluster-sharding/en/headerimage/generatedHeaderImage-1788717337142.jpg"/&gt;&lt;p&gt;Uber has redesigned shard placement in M3DB with fixed size subclusters to limit the impact of node failures, maintenance, and cluster scaling. The approach bounds shard dependencies, preserves replica isolation, and uses a greedy algorithm to select shard migrations while avoiding a separate rebalancing pass and unnecessary data movement.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Database</category>
      <category>Load Balancing</category>
      <category>Database Replication</category>
      <category>Algorithms</category>
      <category>Microservices</category>
      <category>Fault Tolerance</category>
      <category>Open Source</category>
      <category>Scalability</category>
      <category>Time Series Data</category>
      <category>Sharding</category>
      <category>Uber</category>
      <category>Availability</category>
      <category>Distributed Systems</category>
      <category>Clusters</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Mon, 21 Sep 2026 14:37:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/uber-m3db-subcluster-sharding/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Availability-news</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-09-21T14:37:00Z</dc:date>
      <dc:identifier>/news/2026/09/uber-m3db-subcluster-sharding/en</dc:identifier>
    </item>
  </channel>
</rss>
