Notes / Patterns / 05 Distributed Systems Patterns / 04 Consistency Patterns

04 — Consistency Patterns

Strong, Eventual, Causal, Read-Your-Writes, and Monotonic Reads consistency models — what guarantee a client actually gets, and what it costs in latency and availability.

· §202607182250-18 ·
patternsdistributed-systemsbookmaang-prep
Chapter Navigation
On This Page

04 — Consistency Patterns

Purpose

[stub: consistency-patterns]

Metadata

AuthorAmit Singh
Scopepatterns

Local graph

Full graph →

Related notes

Patterns

A book-shaped table of contents for reusable engineering patterns spanning object-oriented design, enterprise architecture, distributed systems, messaging, APIs, cloud infrastructure, observability, security, concurrency, AI/agentic systems, and organizational design — grounded in production experience at scale.

01 — Consensus Patterns

Raft, Paxos, Leader Election, and Quorum — how a distributed system agrees on a single value or leader despite node failures and network partitions.

02 — Coordination Patterns

Distributed Lock, Lease, Heartbeat, Membership, and Gossip — the primitives nodes use to coordinate without a single point of failure.

03 — Replication Patterns

Leader-Follower, Leaderless, Multi-Leader, and Read Replica replication — how copies of the same data stay available and how they diverge under partition.
← All notes
Patterns notes Edit on GitHub
Next → 01 — Message Broker Patterns