ChaptersReplication

Replication

How do you keep copies of the same data on several machines, and what breaks when they disagree?

2 lessons · 19 concepts · ≈ 55 min

Not started

  1. Lesson 1 · ≈ 25 min

    Leader-Based Replication

    One node takes every write and the rest copy it. It's the simplest way to keep many copies of a database, and its failure modes have taken GitHub down twice.

  2. Lesson 2 · ≈ 30 min

    Multi-Leader & Leaderless Replication

    Let more than one node accept writes and you gain availability, local latency and offline editing. You also inherit a question a single leader never faces: when two writes disagree, which one is true?