Growing Distributed Systems
summary
Shows how a Rails app actually becomes distributed with concrete failures and tools: explains CAP theorem tradeoffs, cites Amazon S3 and GitHub outages and Backblaze’s 40 dead hard drives, and compares quorumed systems like Apache Zookeeper to eventually consistent stores and the React distributed database. Covers offline patterns used by Google Docs and Git, unique id generation with Snowflake IDs, service extraction, deployment strategies and testing approaches so you know which parts need strong consistency and which can be eventually correct.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:01What is a distributed system
- 2:46Rules and theory
- 6:15CAP theorem trade-offs
- 8:44Consistency models
- 10:06SQL vs NoSQL
- 11:55From monolith to SOA
- 14:03Extracting services
- 15:30Testing and deploying services
- 16:54Working offline
- 18:40Operational transform
- 20:48API versioning
- 22:11CAP theorem and IDs
- 23:38Q&A
related talks
33mWhy Are Distributed Systems So Hard?
45mDo Distributed Systems they said. It'll be fun they said.
44mDistributed systems and scalability rules
28mWhy Are Distributed Systems So Hard?
29mHorrors of Distributed Systems
41mIntroduction to distributed systems
41mEverything you always wanted to know about highly available distributed databases
22mWhy Are Distributed Systems so Hard?