Operationalizing 19 years of infrastructure via MySQL-as-a-Service
summary
GoDaddy converts 19 years of MySQL sprawl into a MySQL-as-a-Service platform built on Docker containers, an overlay filesystem for separating data from images, a routing/proxy layer and a remediator that auto-rebalances and fails over. Capacity grows from manual ticketing to 15 seconds provisioning; operators are eight people for ~6.5 million databases across 15,000 instances. Images are rebuilt nightly, patches deploy daily into a persistent store (e.g., Ceph), and upgrades (56→57) use backup/restore or replica switchover with near‑zero downtime.
AI-written summary · about
chapters (12)
- 0:00MySQL-as-a-Service intro
- 2:05Infrastructure challenges at scale
- 8:22Evaluating database capacity
- 10:08Containerization in our system
- 14:58Provisioning workflow with routing
- 17:03Legacy infrastructure integration
- 18:49Automated patching process
- 20:32Building repeatable services
- 22:57Autonomous remediation impact
- 23:59Provisioning speed gains
- 24:42Visibility and testing enhancements
- 25:23Summary and future outlook
related talks
41mDemocratizing MySQL: From Cloud Managed to Kubernetes Managed
36mCreate your Own MySQL-as-a-Service that Runs Anywhere Using Kubernetes Operators
21mScaling MySQL at Wordpress.com
01h 02mScaling One of the Largest On-prem Managed MySQL Fleets in India
47mRunning Databases in Docker at Scale
41mThis is Not a Web App: The Evolution of a MySQL Deployment at Google
36mRight-Sizing and Auto-Scaling of MySQL Containers in Kubernetes
26mScaling MySQL with Python