Databases on Kubernetes
summary
Says Percona builds Kubernetes operators using only kubernetes primitives and claims full lifecycle automation: automated provisioning, seamless major and minor upgrades, automated backups and recovery plus integrated PMM metrics and independent horizontal/vertical scaling. Warns lift‑and‑shift monolithic databases into Kubernetes degrades throughput and latency and causes big blast radii; recommends microservices or a portability abstraction, checks for data mobility and sharding needs, and asks why the migration is being done before proceeding.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:23We Community
- 2:09What do we know about Databases at "web" scale?
- 7:49Microservices
- 11:09Unified Abstraction Layer
- 13:57Not Ideal Use-cases
- 17:59How to Have a Good Time
- 22:07Pets vs. Cattle
- 25:24Enter Operators
- 25:51Not All Operators are Created Equally
- 28:02Importance of an Operator
- 30:33A Few Thoughts
- 32:22Why is it confusing?
- 33:09The Best Question
related talks
45mBest Practices for Running Databases on Kubernetes
27mDatabase Infrastructure with Open Source Kubernetes Database Operators
47mFrom a Database in Container to DBaaS on Kubernetes
36mFrom a Database in Container to DBaaS on Kubernetes
31mOpen Source Databases on Kubernetes: Best Practices
19mPrivate DBaaS: Why you Need it, How to Build It
44mFrom a database in container to DBaaS on Kubernetes
45mDatabases on Kubernetes: Why you should care