Deploying #MongoDB on public clouds: Architecture and options
summary
ScaleGrid reports running thousands of MongoDB instances on AWS and Azure and gives concrete rules: replica sets allow up to 50 secondaries but only 7 voting members and modern elections average <5s failover. Backups: mongodump takes hours for hundreds of GB, EBS snapshots plus an fsync lock on secondaries give instant-volume restore without network copy, Atlas uses continuous oplog shipping but costs network transfer for TBs. Azure requires storage-blob snapshots; sharding rebalances can take days. Hybrid local NVMe + EBS preserves performance and durability.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:21Highlevel configuration
- 6:25High availability
- 11:08Multiregion deployment
- 16:30Backups
- 21:46EBS snapshots
- 25:13MongoDB backups
- 28:01Recommended backup model
- 33:03Performance
- 40:28Instance types
- 43:32Network
- 44:25Security
- 45:11Encryption
- 45:39Scaling
- 47:01Shards
- 47:53Operations
- 48:52Query analysis
related talks
43mMulti-Cloud Magic: Leveraging Multi-Cloud Clusters in Real-World Scenarios
24mMoving MongoDB to the Cloud: Strategies and points to consider
40mMulti Cloud Magic: Leveraging Multi Cloud Clusters in Real World Scenarios
42mLeveraging Multi-Cloud Clusters in Real-World Scenarios
40mMongoDB Backups Overview
31mMongoDB: Advantages of an Open Source NoSQL Database
39mCosmos DB for MongoDB: Choosing the right architecture Q&A
53mManaging enterprise JSON workloads with Amazon DocumentDB