Private DBaaS: Why you Need it, How to Build It
summary
Argues that running private DBaaS with Percona Kubernetes operators and Kubernetes removes vendor lockin, preserves data control, and automates toil; cites CNCF figures (96% of orgs try/run Kubernetes, 81% use operators) and lists MySQL, Postgres, Mongo operators used in production by customers (Nokia, Pure Storage, VMware). Describes three adoption patterns—direct k8s access, CI/CD integration, and customer platforms—and offers a turnkey alternative: PMM DBaaS UI/API that provisions, backs up, monitors, and restores databases without developer Kubernetes knowledge.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:56DBaaS hides scary complexity
- 5:37Public vs Private
- 10:12We chose Kubernetes and Operators
- 12:56Operators are not green field anymore
- 14:37How do Operators work?
- 16:14Okay, how do I build Private DBaaS with Operators?
related talks
36mFrom a Database in Container to DBaaS on Kubernetes
44mFrom a database in container to DBaaS on Kubernetes
17mWhy Public Database as a Service is Prime for Open Source Distribution
27mDIY DBaaS with Percona Kubernetes Operators
47mFrom a Database in Container to DBaaS on Kubernetes
30mComposing a Multi Database DBaaS from Open Source Kubernetes Operators
17mThe future of databases is being decided for you
34mDatabases on Kubernetes