Empowering Engineers With a Database DevOps Strategy
summary
Argues that empowering engineers requires measurable wins: track time to deliver and deploy metrics, automate the smallest headache (tickets, PRs, DB provisioning) and iterate with a feedback loop. Warns that databases break assumptions—Postgres sizing and schema changes block deploys, serverless can be costly—so platform work focuses on templates with guard rails, not unlimited choices. Tools mentioned include AWS console, Backstage-style IDPs and Slack integrations; common failures are choosing tooling before metrics and inventing new communication channels.
AI-written summary · about
chapters (7)
- 0:00Introduction and welcome
- 1:08What is DevOps
- 6:49Platform engineering explained
- 10:16Database challenges in DevOps
- 12:02What works in strategy
- 13:26Common pitfalls to avoid
- 15:55Tactical advice and closing
related talks
33mBringing DevOps To The Database
36mUnlocking the Benefits of Database DevOps and Automation
27mDevOps and the Database Bottleneck
31mDevOps Practices for the Database Team
23mBridging the DevOps Gap in Modern Data Teams
37mPlatform Engineers Must Change Developers and Databases - And Here Is How
46mDatabase DevOps - It is Possible!
06mWhen Database Meets DevOps