MongoDB Atlas vs managed community edition
summary
Licensing changes since SSPL change (Oct 16 2018) force cloud providers to either license MongoDB commercially or hard‑fork the last AGPL code, so Atlas bundles proprietary features like Atlas Search, Realm, Data Lake, BI connector and controls binaries and scaling. Atlas requires three-node replica sets per shard, blocks custom binaries and makes exit harder; DocumentDB and Cosmos drop newer Mongo features or transactions. Managed community options include Percona Server for MongoDB with custom builds, open tooling (PMM) and hands‑on expertise to fix shard keys, indexes and migrations.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:38Controversial
- 1:49MongoDB as a service
- 3:13Managed services
- 4:58Community editions
- 5:50Technology vs ecosystem
- 6:54Unique Atlas features
- 12:37Other providers
- 14:08Cloud providers
- 14:41True hard forks
- 17:30Huawei Document Database Service
- 18:16IBM Cloud Databases
- 20:13Polyglot Services
- 22:38Pythians
- 24:00Percona
- 25:57Platform Providers
- 26:28ScaleGrid
- 28:33Kubernetes
- 28:46Kubernetes operators
- 30:45M Clusters
- 31:39Community
- 33:30Small deployments
- 35:53Options
- 39:21Expertise
- 42:45Is Atlas bad
- 45:03Community to action
related talks
02mOpen Source Force Multipliers
53mMongoDB Atlas
20mMongoDB Atlas: more than just a database
40mThe rise of the developer data platform
37mThe State of MongoDB, Its Open Source Community, and Where Percona Is Going With It
09mOpen Software for MongoDB Where Percona Fits
50mDeploying #MongoDB on public clouds: Architecture and options
32mFrom MongoDB to Postgres: Building an Open Standard for Document Databases