ChaptersDistributed Systems

Distributed Systems

What can you know, and agree on, when networks drop messages and clocks lie?

4 lessons · 30 concepts · ≈ 1 h 40 min

Not started

  1. Lesson 1 · ≈ 30 min

    The Trouble with Distributed Systems

    On one machine, things work or they crash. Across a network, a silent peer might be dead, slow, paused or cut off, and you can't tell which. Clocks drift, processes freeze, and the only truth you get is the messages that arrive.

  2. Lesson 2 · ≈ 20 min

    Time, Clocks & Ordering

    Machines can't agree on what time it is, but they can agree on what caused what. Logical clocks order events without trusting any clock; hybrid clocks and TrueTime put physical time back, carefully.

  3. Lesson 3 · ≈ 25 min

    Consistency Models

    “Strongly consistent” is not a spec. A consistency model is the exact contract for what a read may return while copies disagree, and the strongest ones cost you availability, latency, or both.

  4. Lesson 4 · ≈ 25 min

    Consensus

    Getting several machines to agree on one leader, one log, one answer, while any of them may crash and the network may lie about which. Raft and Paxos solve it with one idea, the overlapping majority, and pay for it in round trips.