MySQL in the Cloud
summary
Comparison of cloud DBaaS: Amazon RDS is the most feature-complete and offers MySQL 5.6 but restricts no my.cnf access and exposes only ~283 tunables vs 523 upstream, supports Multi‑AZ synchronous replicas at about multi‑AZ +50% cost, and enforces automated minor upgrades with no online 5.5→5.6 upgrade (dump/reload required). HPCloud DBaaS is beta and scriptable via HPCloud Trove CLI (free but limited), Rackspace still ships MySQL 5.1, and AWS offers provisioned IOPS 30k/3TB for predictable throughput; running MySQL on compute + Galera or MHA gives full control.
AI-written summary · about
chapters (28)
- 0:00Intro
- 0:53whoami
- 1:28Agenda
- 2:27MySQL as a service
- 3:33New way of deployment
- 6:17Your choices today
- 8:23Whom we won't be covering
- 8:49Regions & Availability Zones
- 15:54Who manages this?
- 17:02MySQL versions
- 19:24Access methods
- 28:11Costs: Rackspace
- 28:58Costs: Google
- 29:42Costs: HP Cloud
- 30:02Where do you host your application?
- 30:47RDS: Multi-AZ
- 32:08External replication
- 33:29MySQL 5.6, MariaDB
- 34:59Getting started
- 36:18Handling backups
- 37:02Monitoring
- 38:00Storage Engines
- 39:34High Availability
- 40:25Unsupported features
- 41:08Provisioned IOPS
- 44:04Roadmaps?
- 44:38Running MySQL in EC2
- 46:51Some closing thoughts
related talks
29mRunning MySQL on AWS
32mMySQL on the Cloud: a Journey from Virtual Machines to Serverless Deployments
40mCloud Databases: Pros and Cons
53mMySQL in the Cloud: DBaaS vs Kubernetes
28mMove to Managed Databases
01h 05mDatabase management made simple - Amazon RDS (Part 1 and 2)
25mData in the Cloud
50mThe Great Open Cloud Shootout