Lightning Talk: Continuous Delivery…except for Database Changes
summary
Continuous delivery often excludes database changes, leaving DBAs as gatekeepers while apps ship faster; organizations that adopt database change management see 3.4× more likely elite performance and rate good documentation 3.8 highest, per DORA. The remedy is automating schema deployment with schema-management tooling like Liquibase schema management, removing low‑value manual tasks, bringing DBAs into the pipeline, and delivering safe, repeatable database migrations that match application release velocity.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 1:26Automation and forgotten data services
- 2:57DBAs as sentinels of data
- 4:02New Jersey gas pump analogy
- 5:28Low-hanging fruit for DBAs
- 6:33Database history since 1979
- 7:36Neglect of DBAs in modern practices
- 9:00Expanding CD tent to include DBAs
- 10:25Call to action for DBAs
related talks
45mEnabling Continuous Delivery with Database Practices
05mMaking Database Changes a Tier one Artifact
46mDatabase DevOps - It is Possible!
31mDevOps Practices for the Database Team
21mApplying Continuous Delivery to Database Schema
31mHelp! My Database Is The Bottleneck
27mDevOps and the Database Bottleneck
38mGetting Along With Your Db Ops Team