The shell game called eventual consistency

on YouTube ↗25m

" summary

Argues that cloud-scale systems favor availability over strong consistency and that eventual consistency is the norm, not a bug, citing CAP theorem and saying ~90% of systems are CP-style but many opt AP for scale; recommends concrete tools and patterns—NoSQL, CQRS, queues, long polling, localStorage, WebSockets/HTTP2—for UI strategies (disable + poll, thank-you screens, fake local render, async notifications), warns about conflicts and advises tracing, compensations and delaying charges.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 1:55Agenda
3. 2:38Cap Theorem
4. 10:16Eventual Consistency
5. 22:11When the System Fails How Do You Handle a Possible Data Loss

" related talks

• 39mDealing with eventual consistencyDennis van der Stelt · Øredev 2019
• 44mDistributed systems and scalability rulesOleg Tsal-Tsalko · JavaDay 2013
• 38mEventual Consistency: A Question of Time and ExpectationsSuzy Zimmer, Pierre Charrasse · Voxxed Days Luxembourg 2026
• 30mData Consistency Patterns in Cloud Native ApplicationsRyan Knight · Scale By The Bay 2018
• 52mEventual Consistency in a Stateful ServiceDmitriy Isaev · HighLoad++ 2023
• 59mCQRS pitfalls and patternsUdi Dahan · NDC Oslo 2023
• 15mRethinking Safe Consistency in Distributed Object-Oriented ProgrammingGuido Salvaneschi, Pascal Weisenburger, Mirko Köhler, Nafise Eskandani, Alessandro Margara · OOPSLA 2020
• 01h 03mArchitectural patterns for the cloudMahesh Krishnan · NDC London 2019