Part 1 of 6 · 1 min read
Why this page follows consistency models
In this module you will
- State the CAP trade-off correctly: when a network fault happens, choose consistency or availability.
- Explain why "pick two of three" is a misleading way to say it.
- Describe a CP and an AP behaviour with a three-node example.
- Explain PACELC and the latency cost of strong consistency when nothing is broken.
- Use the ideas in an interview answer without overclaiming.
Module 6 ended with a price: a linearizable system gives up something when the network fails. That price has a famous name, and it is also the most misquoted idea in system design. This page gives the careful version. The books used are "System Design Interview" (which gives the interview-style view), "Designing Data-Intensive Applications" (which criticises it) and "Understanding Distributed Systems" (which adds PACELC). The numbers are made up to show the idea, unless the text names a book.