<?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>Durability on Momo Engineering Journal</title><link>/categories/durability/</link><description>Recent content in Durability on Momo Engineering Journal</description><image><title>Momo Engineering Journal</title><url>/images/og-image.png</url><link>/images/og-image.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 07 Oct 2026 01:35:45 -0600</lastBuildDate><atom:link href="/categories/durability/index.xml" rel="self" type="application/rss+xml"/><item><title>R3: Write Durability — fsync-Before-Ack, Survivor Quorum</title><link>/posts/021-r3-write-durability-quorum/</link><pubDate>Thu, 27 Aug 2026 19:24:05 +0000</pubDate><guid>/posts/021-r3-write-durability-quorum/</guid><description>Ack only what survived: fsync/group-commit durability barrier, survivor quorum, and read-your-writes — the write-side of the P0 stack.</description></item><item><title>R2: Degraded-Read Survivor Fallback and Self-Heal</title><link>/posts/020-r2-degraded-read-self-heal/</link><pubDate>Thu, 27 Aug 2026 10:14:18 +0000</pubDate><guid>/posts/020-r2-degraded-read-self-heal/</guid><description>When a local replica is corrupted or missing, degraded read fetches from healthy survivors transparently, while a background rebuild loop restores cluster redundancy.</description></item><item><title>R1: Failure-Domain-Aware Placement</title><link>/posts/019-r1-failure-domain-placement/</link><pubDate>Wed, 26 Aug 2026 23:52:57 +0000</pubDate><guid>/posts/019-r1-failure-domain-placement/</guid><description>Replicas must not ride in the same rack: CRUSH weights become rack/zone/DC-aware so a single domain failure can&amp;rsquo;t lose the data.</description></item></channel></rss>