CSE Roadmap

Common tier · about 4 hours · 8 parts

Part 1 of 8 · 1 min read

Why this page comes after lag

In this module you will

  • Say when a design needs more than one place to accept writes, and what it costs.
  • Describe how write conflicts arise and four ways to settle them, with the data loss of each.
  • Explain read repair and anti-entropy in a leaderless store.
  • Pick n, w and r for a quorum, check the condition w + r > n, and count the failures tolerated.
  • Explain sloppy quorums and hinted handoff, and why they give up a guarantee.

A single leader is simple, but all writes pass through one place. If that place is far away or fails, writes stop. Two other designs let several nodes accept writes. They fix the problem and bring a new one: two nodes can accept different values for the same item at the same time. The tier is Common. The numbers are made up to show the idea, unless the text names a book.