Building a Self Service DBaaS for Your Internal Developer Platform
summary
A runnable internal DBaaS is built by wiring MongoDB Atlas to Kubernetes via the Atlas Kubernetes Operator, storing Atlas project and deployment CRs in GitHub, and letting Argo CD pick up git pushes so the operator reconciles and creates Atlas projects and clusters automatically. Developers never need kubectl or cluster access, teams use shared YAML templates, configuration drift is reduced by periodic reconciliation, and onboarding, security scoping, and cost attribution improve while deployments become self‑service and repeatable.
AI-written summary · about
chapters (8)
- 0:00Self-service DBaaS intro
- 2:54Infrastructure pain points
- 7:24GitOps & Kubernetes tools
- 10:36Platform engineering for scale
- 14:52Demo: DB operator deploy
- 18:49Demo: GitOps & Argo CD
- 22:31Centralized DBaaS benefits
- 25:59Q&A: Access & Atlas on-prem
related talks
14mBuilding a self service DBaaS
19mPrivate DBaaS: Why you Need it, How to Build It
27mDIY DBaaS with Percona Kubernetes Operators
20mMongoDB Atlas: more than just a database
34mChoose Your Own Adventure: The Dignified Pursuit of a Developer Platf...
37mBuilding a self-service kubernetes platform for python developers
40mThe rise of the developer data platform
25mUpdating Databases the GitOps Way