Getting Along With Your Db Ops Team
summary
Describes bringing engineering and databases under a shared DB acceptance policy that enforces ACID-like rules for deployments: each DB-involved deploy must be progressive or transparently rolled back, migrations tracked in source control (git) and via Liquibase, schema examples include explicit primary keys and correctly sized fields, pipelines push from dev→staging→prod, restores and daily tested backups are automated, explain plans and monitoring validate performance, and rollback scripts plus audit trails prove what changed.
AI-written summary · about
chapters (6)
- 0:00Intro
- 1:38ACID
- 10:09In Practice - Database Schema
- 17:36In Practice - DBA
- 25:00Getting Along with your DB Ops Team
- 32:22Troubleshooting tips
related talks
31mDevOps Practices for the Database Team
45mEnabling Continuous Delivery with Database Practices
36mUnlocking the Benefits of Database DevOps and Automation
50mBringing DevOps to the Database
11mLightning Talk: Continuous Delivery…except for Database Changes
46mDatabase DevOps - It is Possible!
31mHelp! My Database Is The Bottleneck
27mDevOps and the Database Bottleneck