Causal Consistency in MongoDB Explained in Detail
summary
The talk explains how MongoDB implements causal consistency to avoid anomalies of eventually consistent distributed databases where reads on different nodes may not reflect recent writes. It describes the problem with eventual consistency reducing throughput and shows how adding causal consistency lets systems scale better without requiring application code changes, focusing on MongoDB’s design and mechanisms for providing those guarantees.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 8:15Formal definition
- 11:50Sharding and replication
- 15:29Cluster time implementation
- 20:47Preventing time manipulation
- 27:06Causal consistency in sessions
- 32:23Q&A
related talks
33mCausality is simple #bbuzz
49mThe cost of MongoDB ACID transactions in theory and practice
10mEverything You Know About MongoDB is Wrong
52mEventual Consistency in a Stateful Service
53mEventual consistency in pizza production
12mFault-Tolerant Replication with Pull-Based Consensus in MongoDB
01h 00mBeyond Eventual Consistency
25mThe shell game called eventual consistency