<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>reliability on semikolan</title>
    <link>https://semikolan.me/tags/reliability/</link>
    <description>Recent content in reliability on semikolan</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 27 Jul 2026 21:19:11 +0530</lastBuildDate>
    <atom:link href="https://semikolan.me/tags/reliability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Year of Reading Postmortems</title>
      <link>https://semikolan.me/blog/a-year-of-reading-postmortems/</link>
      <pubDate>Tue, 02 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://semikolan.me/blog/a-year-of-reading-postmortems/</guid>
      <description>&lt;p&gt;I spent last year reading one public postmortem a week — outages from companies large enough to be forced into candor. I expected exotic failures. What I found was the same three or four stories wearing different logos.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-retry-that-became-the-outage&#34;&gt;The retry that became the outage &lt;a class=&#34;anchor&#34; href=&#34;#the-retry-that-became-the-outage&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The single most common shape: a small failure triggers automatic retries, the retries multiply the load, and the load turns a blip into a self-sustaining fire. The system&amp;rsquo;s own recovery mechanism is the accelerant.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
