From a database in container to DBaaS on Kubernetes
summary
Claims Kubernetes can host a full DBaaS that runs anywhere Kubernetes runs and avoid cloud lock‑in by using open source tooling; operators are necessary for day‑two features like backups, self‑healing, scaling and rolling upgrades, while raw Helm/containers only solve provisioning. Percona ships production operators for MySQL/Postgres/Mongo and is building Percona Everest as an RDS‑like open source layer. Watch for storage tuning (NVMe/local or proper block volumes) and anti‑affinity rules to avoid co‑located failures.
AI-written summary · about
chapters (8)
- 0:00Introduction and open source journey
- 6:13Docker for databases in production
- 11:34Databases on Kubernetes challenges
- 19:52Operators for database lifecycle
- 25:15Database as a Service benefits and risks
- 33:23Kubernetes as cloud commodity interface
- 37:42Future of open source and DBaaS
- 40:19Q&A on performance and user experience
related talks
36mFrom a Database in Container to DBaaS on Kubernetes
47mFrom a Database in Container to DBaaS on Kubernetes
19mPrivate DBaaS: Why you Need it, How to Build It
27mDIY DBaaS with Percona Kubernetes Operators
27mDatabase Infrastructure with Open Source Kubernetes Database Operators
34mDatabases on Kubernetes
31mOpen Source Databases on Kubernetes: Best Practices
30mComposing a Multi Database DBaaS from Open Source Kubernetes Operators