Bringing DevOps To The Database
summary
Argues databases resist DevOps because they are stateful and legacy, and offers concrete, repeatable steps drawn from a decade of study and many case studies. Recommends schema as code, automated migrations and better monitoring; warns that naive automation can both fix problems and cause data drift (a flash-sale outage caused by running a command on the wrong server but the site is back online the same morning). Recommends tooling like Percona Toolkit plus graduated, low-risk rollouts.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:22Backstory
- 8:35Mainstream Trends
- 10:30DevOps in the Database
- 13:50Database Challenges
- 16:36Dysfunction
- 18:53Tooling
- 20:06Data Bases
- 21:53Capability Maturity
- 23:36Tools
- 29:55Internal Resistance
- 31:32Resources
- 32:35Outro
related talks
27mDevOps and the Database Bottleneck
36mUnlocking the Benefits of Database DevOps and Automation
31mDevOps Practices for the Database Team
17mEmpowering Engineers With a Database DevOps Strategy
46mDatabase DevOps - It is Possible!
06mWhen Database Meets DevOps
50mBringing DevOps to the Database
23mBridging the DevOps Gap in Modern Data Teams