Strategies for Reliable Database Schema Migrations

on YouTube ↗27m

" summary

A real outage occurs when an enum alter triggers a full table rewrite and a lock that lasts around four hours; the recovery shows human review and CI missed that risk. The solution is Database schema as code with a planner and Atlas’s migration analysis engine that flags destructive and backward-incompatible changes, plus unit tests for DB logic, data-migration tests, CI-time warnings and migration checks (txar) that run pre-deploy — these catch risky alters before production.

AI-written summary · about

" chapters (11)

1. 0:00Introduction and Speaker Background
2. 1:04Developer Horror Story: A Migration Gone Wrong
3. 4:23Postmortem Analysis: Understanding the Outage
4. 6:45The Importance of Reliable Schema Changes
5. 7:45Strategy 0: Automate Your Schema Changes
6. 9:40Strategy 1: Database Schema as Code
7. 12:06Strategy 2: Testing Database Logic with Unit Tests
8. 14:58Strategy 3: Testing Data Migrations
9. 17:42Strategy 4: Automating Risk Detection in Migrations
10. 24:14Strategy 5: Pre-Migration Checks
11. 25:52Conclusion and Recap of Strategies

" related talks

• 28mSchema-as-Code: Developer platforms and database schema changesRotem Tamir · DevOpsDays Singapore 2024
• 33mDatabase Schema Migrations with Zero DowntimeMichiel Rook · DevOpsDays Copenhagen 2019
• 37mDatabase Schema Migrations with Zero DowntimeMichiel Rook · PHP UK Conference 2018
• 59mNavigating the Challenges of CI /CD for Relational Database Schema ChangesMichael Carducci · Great International Developer Summit 2024
• 31mHelp! My Database Is The BottleneckStephanie Herr · DevOpsDays Philadelphia 2017
• 35mDatabase migrations without downtimeMichiel Rook · Dutch PHP Conference 2017
• 33mAvoid Toll Roads: Deploying Declarative Database Schema ChangesRotem Tamir · DevOpsDays Madrid 2023
• 40mrails db:migrate:safelyMatt Duszynski · RailsConf 2019