Eventual consistency in pizza production
summary
Explains how data consistency problems arise when a system moves from a single database to multiple databases, using an analogy of pizza production. Covers eventual consistency as an approach to maintain integrity across separate data stores and discusses practical implications for backend systems when transactions no longer span all data.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:58System growth issues
- 4:04Monolith splitting
- 7:04Distributed system problems
- 10:58Data consistency
- 13:49Eventual consistency choice
- 16:43Guaranteed delivery solution
- 18:31Event duplication and order
- 21:07Error handling and retries
- 25:12Monitoring and scaling
- 27:44Summary and benefits
- 29:53Implementation recommendations
- 30:57Q&A
related talks
52mEventual Consistency in a Stateful Service
27mData Consistency in Microservices Architecture
38mEventual Consistency: A Question of Time and Expectations
01h 00mBeyond Eventual Consistency
42mCausal Consistency in MongoDB Explained in Detail
25mThe shell game called eventual consistency
28mPractical Approaches To Scaling Distributed Transactions
44mDistributed systems and scalability rules