<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fault-Tolerance on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/fault-tolerance/</link>
    <description>Recent content in Fault-Tolerance on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/fault-tolerance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Circuit Breaker Patterns: Envoy vs HAProxy vs Linkerd 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-01-self-hosted-circuit-breaker-envoy-haproxy-linkerd-fault-tolerance-guide/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-01-self-hosted-circuit-breaker-envoy-haproxy-linkerd-fault-tolerance-guide/</guid>
      <description>&lt;p&gt;When a downstream service starts failing, your entire application can cascade into failure. Circuit breakers prevent this by detecting unhealthy backends and short-circuiting requests before they pile up. Rather than waiting for connections to time out, a circuit breaker trips open, fails fast, and gives the failing service time to recover.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
