Schema-as-Code: Developer platforms and database schema changes
summary
Shows an actual outage root cause where adding an ENUM value in MySQL triggers a full table rewrite and 100% CPU spike, then demonstrates a practical platform: Atlas auto-plans migrations with the migrate diff command, runs static safety checks via a GitHub Action against ~30 configurable policies, and blocks risky changes. The demo deploys safe migrations to production through Atlas Cloud and a Kubernetes operator, and the automated workflow prevents the destructive ENUM change that caused the outage.
AI-written summary · about
chapters (7)
- 0:00Rotem Intri
- 1:07Developer Horror Story
- 3:59The system blows up.
- 8:19Migrations are risky business
- 10:55DORA Metrics
- 15:08Venn Diagram: DevOps, SRE, Platform Engineering
- 19:00Live Demo schema change
related talks
27mStrategies for Reliable Database Schema Migrations
37mDatabase Schema Migrations with Zero Downtime
33mAvoid Toll Roads: Deploying Declarative Database Schema Changes
33mDatabase Schema Migrations with Zero Downtime
31mHelp! My Database Is The Bottleneck
52mAutomatic MySQL schema management with Skeema
37mPlatform Engineers Must Change Developers and Databases - And Here Is How
31mBeyond Alembic and Django Migrations