The New MongoDB Sharding Architecture
summary
Explains MongoDB sharding vs replication: replication increases reliability and read scaling by copying data across more machines, while sharding splits data to scale writes and compute but adds failure points. Describes how many MongoDB deployments combine sharding with replication, greatly increasing hardware needs and leading to deployments with hundreds or thousands of servers.
AI-written summary · about
chapters (7)
- 0:00Introduction to new architecture
- 7:07Data replication basics
- 12:03Load distribution and reads
- 17:58Hashing and ring structure
- 21:38Adding and removing nodes
- 24:35Data balancing issues
- 26:21Q&A
related talks
34mScaling Applications with MongoDB: Best Practices and Challenges
24mWhen and How Should you Shard?
45mSharding and Things We'd Like To See Improved
37mBuilding MongoDB Replica
10mEverything You Know About MongoDB is Wrong
23mSharding for hyperscale and geographically distributed relational databases
50mApproaches to implementing sharding in modern [No]SQL systems
25mHybrid Applications with MongoDB and RDBMS