<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>High Availability on Vubon Notes</title><link>https://vubon.me/tags/high-availability/</link><description>Recent content in High Availability on Vubon Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 08 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://vubon.me/tags/high-availability/index.xml" rel="self" type="application/rss+xml"/><item><title>System Design Interview: Partial Failure &amp; Durability</title><link>https://vubon.me/posts/system-design-interview-partial-failure/</link><pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate><guid>https://vubon.me/posts/system-design-interview-partial-failure/</guid><description>&lt;p>After talking about idempotency, I thought I&amp;rsquo;d share another good follow-up question:&lt;/p>
&lt;p>&lt;strong>&amp;ldquo;What happens if your service crashes in the middle of a request?&amp;rdquo;&lt;/strong>&lt;/p>
&lt;p>Let&amp;rsquo;s say:&lt;/p>
&lt;ul>
&lt;li>transfer record inserted ✅&lt;/li>
&lt;li>ledger update started ❌&lt;/li>
&lt;li>database connection drops&lt;/li>
&lt;li>service dies&lt;/li>
&lt;/ul>
&lt;p>Now you have partial data.&lt;/p>
&lt;p>And in payment systems, partial success is usually worse than failure.&lt;/p>
&lt;p>




&lt;figure class="">
 
 
 &lt;div class="img-container">
 &lt;img loading="lazy" alt="What if your service crashes in the middle of a request?" src="https://vubon.me/images/partial-failure-durability.png">
 &lt;/div>
 

 
&lt;/figure>
&lt;/p>
&lt;hr>
&lt;h2 class="heading" id="the-first-answer-most-people-give">
 The first answer most people give
 &lt;a class="anchor" href="#the-first-answer-most-people-give">#&lt;/a>
&lt;/h2>
&lt;p>👉 &lt;em>Use database transactions (ACID).&lt;/em>&lt;/p></description></item></channel></rss>