<?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 vnykmshr</title><link>https://blog.vnykmshr.com/writing/tags/reliability/</link><description>Recent content in Reliability on vnykmshr</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 16 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.vnykmshr.com/writing/tags/reliability/index.xml" rel="self" type="application/rss+xml"/><item><title>The happy path</title><link>https://blog.vnykmshr.com/writing/plumbing-and-abstractions/</link><pubDate>Fri, 16 Jan 2026 00:00:00 +0000</pubDate><guid>https://blog.vnykmshr.com/writing/plumbing-and-abstractions/</guid><description>&lt;p&gt;The diagrams always show the happy path. Request goes in, response comes out, maybe a queue in between. Three boxes and two arrows. The failure modes live in the whitespace.&lt;/p&gt;
&lt;p&gt;Distributed systems work at demo time. In production, the third service fails after the first two succeeded: the debit went through, the credit went through, the write to the audit log dropped on a socket timeout, and both sides of the transfer had moved without anything recording &lt;em&gt;that&lt;/em&gt; they had moved. The same row was about to be replayed the next morning. Someone noticed the mismatch six weeks later, at the end of the month, in a spreadsheet one of the ops people was maintaining by hand.&lt;/p&gt;</description></item></channel></rss>