<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Distributed Cache - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Distributed Cache Articles feed</description>
    <item>
      <title>Article: One Cache to Rule Them All: Handling Responses and In-Flight Requests with Durable Objects</title>
      <link>https://www.infoq.com/articles/durable-objects-handle-inflight-requests/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Cache-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/durable-objects-handle-inflight-requests/en/headerimage/durable-objects-handle-inflight-requests-header-1769161248259.jpg"/&gt;&lt;p&gt;Traditional caching fails to stop "thundering herds" where multiple clients trigger the same work during a miss. This article proposes using Cloudflare Durable Objects to treat in-flight work and finished results as two states of one cache entry. By routing to a single owner, systems eliminate redundant tasks. This pattern replaces complex locks with simple promises, simplifying the system design.&lt;/p&gt; &lt;i&gt;By Gabor Koos&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>Distributed Cache</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Wed, 28 Jan 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/durable-objects-handle-inflight-requests/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Cache-articles</guid>
      <dc:creator>Gabor Koos</dc:creator>
      <dc:date>2026-01-28T09:00:00Z</dc:date>
      <dc:identifier>/articles/durable-objects-handle-inflight-requests/en</dc:identifier>
    </item>
  </channel>
</rss>
