<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title> - Distributed Systems</title>
    <link rel="self" type="application/atom+xml" href="https://sysrex.com/tags/distributed-systems/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://sysrex.com"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2025-01-20T00:00:00+00:00</updated>
    <id>https://sysrex.com/tags/distributed-systems/atom.xml</id>
    <entry xml:lang="en">
        <title>Retries, Backoff, and Jitter: Why Naive Retry Logic Makes Outages Worse</title>
        <published>2025-01-20T00:00:00+00:00</published>
        <updated>2025-01-20T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://sysrex.com/posts/retries-backoff-jitter/"/>
        <id>https://sysrex.com/posts/retries-backoff-jitter/</id>
        
        <summary type="html">&lt;p&gt;&quot;Just retry the request&quot; is one of the most reasonable-sounding pieces of
advice in distributed systems, and one of the easiest to get badly wrong.
Done carelessly, retries don&#x27;t make your system more resilient — they turn
a small, recoverable blip into a full outage.&lt;&#x2F;p&gt;</summary>
        
    </entry>
</feed>
