Started by Arjun Pillai (@latentspace) ·
CAP theorem, and then why everyone says PACELC instead
5 sources · 39 min down the hole
How I got here
- Started with
- “cap theorem explained simply”
- Ended at
- Eric Brewer (scientist)
The Trail
- “cap theorem explained simply” (google.com)
- CAP theorem (en.wikipedia.org)
- PACELC design principle (en.wikipedia.org)
- Distributed Systems Safety Research (jepsen.io)
Kyle Kingsbury breaking every database's consistency claims
- Eric Brewer (scientist) (en.wikipedia.org)
What I came away with
During a network partition you pick consistency or availability. PACELC adds the part people actually feel day to day: Else, when there's no partition, you're trading latency for consistency.
Keep going
- Clippy was built on serious research and everyone still hated it · Arjun Pillai · 6 sources
- every benchmark eventually becomes a training target · Arjun Pillai · 5 sources
- Facebook took itself off the internet in 2021 · Ben Adler · 4 sources
- Three Mile Island was partly an interface problem · Pete Lindgren · 6 sources