<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Request Coalescing on Nalar</title>
    <link>https://nalar.dev/tags/request-coalescing/</link>
    <description>Recent content in Request Coalescing on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/request-coalescing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go singleflight Shares Only In-Flight Results</title>
      <link>https://nalar.dev/go-singleflight-shares-only-in-flight-results/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/go-singleflight-shares-only-in-flight-results/</guid>
      <description>&lt;p&gt;&lt;code&gt;singleflight.Group&lt;/code&gt; suppresses duplicate function executions only while an operation for the same key is in flight. Concurrent callers can receive one shared result, but a caller arriving after completion starts a new execution. The group is therefore a request-coalescing mechanism, not a result cache.&lt;/p&gt;&#xA;&lt;p&gt;This boundary affects cache fills, metadata refreshes, backend reads, and other keyed operations that can attract bursts of identical concurrent work. A group can reduce simultaneous pressure on the backing operation without extending the lifetime of its returned value.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
