Sharding in MongoDB
summary
Explains how MongoDB’s built-in sharding provides horizontal scalability by distributing disk, RAM and CPU load across a cluster, with automatic sharding and resharding and transparent client access. Focuses on the critical choice of shard key (which cannot be changed later) and describes using Tag Aware Sharding to map data to specific shards for requirements like keeping a user’s primary data on the same continent or separating active shards from archival ones.
AI-written summary · about
chapters (14)
- 0:00Introduction to sharding
- 3:30What is sharding
- 9:01MongoDB architecture
- 12:48Config server setup
- 15:47Adding a shard to cluster
- 17:55Horizontal scaling principles
- 19:23Enabling sharding for collection
- 21:52Geographic data distribution
- 23:21Query types in sharded MongoDB
- 27:24Sharding use cases
- 29:52Choosing the right shard key
- 33:18Shard key requirements
- 35:51Monotonic key growth issues
- 38:24Conclusion and Q&A
related talks
24mWhen and How Should you Shard?
45mSharding and Things We'd Like To See Improved
34mScaling Applications with MongoDB: Best Practices and Challenges
50mApproaches to implementing sharding in modern [No]SQL systems
25mHybrid Applications with MongoDB and RDBMS
23mSharding for hyperscale and geographically distributed relational databases
41mHow to Survive Under Load with 100TB in an Unsharded MongoDB
32mSharding for mission-critical, internet-scale apps