https://blog.rtshkmr.com/tags/reliability/Recent content in Reliability on An observer's logHugoenhttps://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/consistency-models/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/consistency-models/<p>🔴 P0 &mdash; <em>the spectrum from linearisability to eventual consistency</em></p>https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/cap-theorem-and-pacelc/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/cap-theorem-and-pacelc/<p>🔴 P0 &mdash; <em>the foundational impossibility result and its more nuanced successor</em></p>https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/quorum-reads-writes/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/quorum-reads-writes/<p>🔴 P0 &mdash; <em>the mathematical foundation for consistency in replicated systems</em></p>https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/raft-consensus/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/raft-consensus/<p>🟠 P1 &mdash; <em>the understandable consensus algorithm; know conceptually, not implementation details</em></p>https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/two-phase-commit/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/two-phase-commit/<p>🔴 P0 &mdash; <em>the classical distributed transaction protocol and why it&rsquo;s limited</em></p>https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/saga-pattern/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/saga-pattern/<p>🔴 P0 &mdash; <em>the distributed transaction pattern for microservices; critical for Stripe payment flows</em></p>https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/timeout-strategies/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/timeout-strategies/<p>🔴 P0 &mdash; <em>the most fundamental reliability mechanism; every network call needs one</em></p>https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/circuit-breaker/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/circuit-breaker/<p>🔴 P0 &mdash; <em>prevents cascading failures by stopping calls to a failing service</em></p>https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/retry-with-backoff/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/retry-with-backoff/<p>🔴 P0 &mdash; <em>the default error recovery mechanism; Stripe definitely asks about this</em></p>https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/bulkhead-isolation/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/bulkhead-isolation/<p>🟠 P1 &mdash; <em>isolating failures so one component&rsquo;s problems don&rsquo;t sink the ship</em></p>https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/ordering-and-causality/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/ordering-and-causality/<p>🟠 P1 &mdash; <em>how distributed systems reason about &ldquo;what happened before what&rdquo;</em></p>https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/Mon, 01 Jan 0001 00:00:00 +0000https://blog.rtshkmr.com/reference/archi/patterns/reliability-and-consistency/