<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Backpressure on Nalar</title>
    <link>https://nalar.dev/tags/backpressure/</link>
    <description>Recent content in Backpressure on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 13 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/backpressure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Request Coalescing Turns Cache Miss Bursts Into Shared Work</title>
      <link>https://nalar.dev/request-coalescing-turns-cache-miss-bursts-into-shared-work/</link>
      <pubDate>Sun, 13 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/request-coalescing-turns-cache-miss-bursts-into-shared-work/</guid>
      <description>&lt;p&gt;A cache entry expires at a single instant, but requests for that entry do not necessarily arrive one at a time. If twenty callers observe the same miss before any caller has repopulated the cache, a conventional cache-aside path can send twenty equivalent reads to the origin. The cache is functioning according to its contract; the concurrency around the miss is creating duplicated work.&lt;/p&gt;&#xA;&lt;p&gt;Request coalescing changes that boundary. Instead of treating each miss as permission to start an origin operation, callers for the same key can share one in-flight operation. One caller becomes the producer of the pending result. Other callers wait for that result rather than starting equivalent work.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
