<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Distributed-Systems on Loop &amp; Retry</title>
    <link>https://loopandretry.github.io/tags/distributed-systems/</link>
    <description>Recent content in Distributed-Systems on Loop &amp; Retry</description>
    <image>
      <title>Loop &amp; Retry</title>
      <url>https://loopandretry.github.io/images/og-default.png</url>
      <link>https://loopandretry.github.io/images/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 13 Jul 2026 18:15:00 -0400</lastBuildDate>
    <atom:link href="https://loopandretry.github.io/tags/distributed-systems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Distributed retry patterns: bounding blast radius across a fleet</title>
      <link>https://loopandretry.github.io/posts/fleet-retry-patterns/</link>
      <pubDate>Mon, 13 Jul 2026 18:15:00 -0400</pubDate>
      <guid>https://loopandretry.github.io/posts/fleet-retry-patterns/</guid>
      <description>A per-step retry cap bounds a step. It never bounds a run, and it never bounds a fleet — twelve workers each retrying &amp;lsquo;reasonably&amp;rsquo; is how you turn one bad deploy into a bill. The four patterns that actually put a ceiling on what a fleet of agents can spend recovering from a failure: shared retry budgets, circuit breakers, decorrelated backoff, and poison quarantine.</description>
    </item>
  </channel>
</rss>
