Navigating Managed Databases for Over a Decade as a Non-DBA
summary
Fifteen years of running AWS RDS teaches concrete rules: migrations to Aurora fail if primary is ahead of replicas so you can be blocked for 6–9 months; autoscaling storage can blow up an ALTER TABLE during a copy so disable it for schema changes; backups and binlogs often double monthly cost so monitor backup storage and reclaim bloat; Graviton changed CPU/memory ratios and caused a crash, so prefer percentage-based tunables, warm replicas before cutover, and validate tricky ops with support tickets.
AI-written summary · about
chapters (9)
- 0:00Introduction to Cloud Databases
- 0:15Early Days with AWS
- 1:24Transition to Managed Databases
- 4:18Challenges and Lessons Learned
- 5:39Interacting with Support
- 7:19Storage and Cost Optimization
- 12:19Scaling and Performance Issues
- 17:26Migration to Aurora
- 24:00Final Thoughts and Recommendations
related talks
37mNavigating Managed Databases for Over a Decade as a Non-DBA
19mManaging Databases at Scale - AWS
26mIntroduction to AWS databases: Modernize your data infrastructure
28mMove to Managed Databases
43mKeep calm and dive deep into newest database innovations
25mMigrate to an AWS database: The freedom to save, grow, and innovate
35mFree to Save, Grow, and Innovate: AWS Databases
40mCloud Databases: Pros and Cons