<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Caching</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Caching 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=Caching</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>Load Balancing</category>
      <category>Caching</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=Caching</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>Cloudflare Details its Migration  to "WordPress Successor" EmDash</title>
      <link>https://www.infoq.com/news/2026/09/cloudflare-emdash-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Caching</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/09/cloudflare-emdash-migration/en/headerimage/generatedHeaderImage-1788551109664.jpg"/&gt;&lt;p&gt;Cloudflare recently documented the migration of its main blog from WordPress to EmDash, the open source content management system developed internally. The new platform is designed to improve performance and caching, and it was tested to handle traffic of up to 7000 requests per second.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>WordPress</category>
      <category>Caching</category>
      <category>migration</category>
      <category>Cloudflare</category>
      <category>Portal/CMS</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Sat, 26 Sep 2026 09:38:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/cloudflare-emdash-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Caching</guid>
      <dc:creator>Renato Losio</dc:creator>
      <dc:date>2026-09-26T09:38:00Z</dc:date>
      <dc:identifier>/news/2026/09/cloudflare-emdash-migration/en</dc:identifier>
    </item>
    <item>
      <title>Cloudflare Cuts 100 TB of Memory from 1.1.1.1 DNS Cache</title>
      <link>https://www.infoq.com/news/2026/09/cloudflare-dns-cache/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Caching</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/09/cloudflare-dns-cache/en/headerimage/generatedHeaderImage-1788755192272.jpg"/&gt;&lt;p&gt;Cloudflare redesigned the in-memory representation of its Big Pineapple DNS cache, reducing the per-entry footprint by 56% and freeing roughly 100 TB of working-set memory across its fleet. The Rust-based changes also increased cache insertion throughput by 43% and reduced lookup latency by 19%, while enabling Cloudflare to increase cache capacity without additional memory.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>DNS</category>
      <category>Scalability</category>
      <category>Caching</category>
      <category>Cloudflare</category>
      <category>Performance</category>
      <category>Infrastructure</category>
      <category>Memory</category>
      <category>Rust</category>
      <category>Distributed Systems</category>
      <category>Optimization</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Wed, 23 Sep 2026 13:22:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/09/cloudflare-dns-cache/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Caching</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-09-23T13:22:00Z</dc:date>
      <dc:identifier>/news/2026/09/cloudflare-dns-cache/en</dc:identifier>
    </item>
  </channel>
</rss>
