Consistency and Replication

TRACK

Client-visible consistency contracts, replication topologies, quorum and repair mechanisms, sharding authority, safe reads, recovery, and production verification.

How can I turn business invariants into explicit read, write, failover, and recovery guarantees across replicated and sharded data?

24 lessons

Continues to Backend Database Operations and Query Performance/ CRDTs and Coordination Avoidance/ Data Architecture and Platforms/ Data Integration, CDC, and Pipelines/ Distributed Messaging and Queue Internals/ Distributed Schedulers and Control Planes/ Distributed Systems Protocols and Labs/ Distributed Testing, Simulation, and Deterministic Replay

LESSONS

  1. 001
    [TODO]
  2. 002
    [TODO]
  3. 003
    [TODO]
  4. 004
    [TODO]
  5. 005
    [TODO]
  6. 006
    [TODO]
  7. 007
    [TODO]
  8. 008
    [TODO]
  9. 009
    [TODO]
  10. 010
    [TODO]
  11. 011
    [TODO]
  12. 012
    [TODO]
  13. 013
    [TODO]
  14. 014
    [TODO]
  15. 015
    [TODO]
  16. 016
    [TODO]
  17. 017
    [TODO]
  18. 018
    [TODO]
  19. 019
    [TODO]
  20. 020
    [TODO]
  21. 021
    [TODO]
  22. 022
    [TODO]
  23. 023
    [TODO]
  24. 024
    [TODO]

← Back to Distributed Systems