<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Resilience on Nalar</title>
    <link>https://nalar.dev/tags/resilience/</link>
    <description>Recent content in Resilience on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/resilience/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Design Circuit Breakers for Cloud Service Dependencies</title>
      <link>https://nalar.dev/circuit-breakers-cloud-service-dependencies/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/circuit-breakers-cloud-service-dependencies/</guid>
      <description>&lt;p&gt;When a downstream service is failing, continuing to send every request can waste threads, sockets, and latency budget while increasing load on the unhealthy dependency. A circuit breaker temporarily fails calls fast after failures cross a threshold.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understand-the-three-states&#34;&gt;Understand the three states&lt;/h2&gt;&#xA;&lt;p&gt;A typical breaker is &lt;strong&gt;closed&lt;/strong&gt; while calls flow normally. It moves &lt;strong&gt;open&lt;/strong&gt; after a configured failure policy is exceeded. After a recovery interval, it becomes &lt;strong&gt;half-open&lt;/strong&gt; and allows a limited number of probes. Successful probes close the circuit; failures open it again.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
