<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bulkheads on Nalar</title>
    <link>https://nalar.dev/tags/bulkheads/</link>
    <description>Recent content in Bulkheads on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/bulkheads/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Bulkheads Isolate Resource Pools Before Failures Spread</title>
      <link>https://nalar.dev/bulkheads-isolate-resource-pools-before-failures-spread/</link>
      <pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/bulkheads-isolate-resource-pools-before-failures-spread/</guid>
      <description>&lt;p&gt;A service can remain healthy at the process level while becoming useless because one workload has consumed every scarce execution resource. A slow dependency can occupy all outbound connections. A noisy tenant can fill every worker slot. A background job can take the same semaphore permits needed by interactive requests.&lt;/p&gt;&#xA;&lt;p&gt;Bulkhead isolation limits that coupling. Instead of letting unrelated work compete for one undifferentiated pool, the system partitions selected resources and gives each class of work a bounded share. Saturation then has a smaller blast radius.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
