4.Replication
Distributed Systems · 7 notes
- 4. Distributed-System Replicationhistorical
Why distributed systems keep multiple replicas of the same data, how replication improves availability and read capacity, and the major design dimensions behind replication.
- 4.1 Multi-Leader Replicationhistorical
Why multiple leaders are useful across regions or offline-capable systems, and how concurrent writes create conflicts that require prevention, detection, or resolution.
- 4.2 Leaderless Replicationhistorical
Leaderless replication with multi-replica reads/writes, quorum-style coordination, version reconciliation, read repair, and anti-entropy.
- 4.3 Single-Leader Replicationhistorical
How leader/follower replication handles writes, reads, initial synchronization, incremental catch-up, leader election, and failover.
- 4.4 Replication Logshistorical
Physical and logical change logs, statement- versus row-oriented replication, and why deterministic replay and schema/storage coupling matter.
- 4.5 Replication Strategieshistorical
Synchronous, asynchronous, and semi-synchronous replication and how acknowledgement rules change latency, durability, availability, and replica lag.
- 4.6 Replication Architectureshistorical
The three common replication topologies: single-leader, multi-leader, and leaderless replication, and the trade-offs each introduces.