Building a self service DBaaS
summary
Concrete pipeline that works end to end: developer writes a YAML describing name, instance size, provider and region, pushes it to a Git repo, Argo CD watches the repo and syncs, the Atlas Kubernetes Operator sees the custom resource and calls the Atlas API to create and manage the database. Prereqs are an Atlas account and API key, a running Kubernetes cluster, operator installed, Argo CD and an infra repo. Notes include t-shirt sizing templates, stricter prod guards, and the claim that 95% of IDPs sit on Kubernetes.
AI-written summary · about
chapters (7)
- 0:00Self-service DBaaS intro
- 1:57Kubernetes as platform
- 4:21Internal dev platforms
- 6:07DBaaS risks
- 8:36Implementation tools
- 9:41Kubernetes operator for database management
- 12:48DBaaS setup with Argo CD
related talks
31mBuilding a Self Service DBaaS for Your Internal Developer Platform
25mUpdating Databases the GitOps Way
19mPrivate DBaaS: Why you Need it, How to Build It
25mHow to Build Modern DBaaS Using CNCF Ecosystem Technologies
34mThe Full Stack Preview: Kubernetes, ArgoCD, and Ephemeral Databases
28mBuilding Self-Service Data Platforms
18mRe-envisioning Local Development and Testing With Cloud Databases
26mChallenges of Managing Stateful Applications in Kubernetes