CSE Roadmap

Core tier · about 2 hours · 5 parts

Part 1 of 5 · 1 min read

Why this page comes first

In this module you will

  • Define replication lag, and explain why an asynchronous follower always has some.
  • Define read-your-writes, monotonic reads, and consistent prefix reads as three specific guarantees.
  • Match a concrete user-facing bug to the specific guarantee that was violated.
  • Explain a practical fix for each of the three guarantees.

The previous page covered asynchronous followers as a way to scale reads without slowing down writes. This page covers the direct cost of that choice. A follower that is slightly behind can show a user something confusing, and this page names the three specific ways that confusion shows up.