Treat schema and data changes as part of the engineering workflow, with explicit transitions and repeatable verification.
What to look for
- 01
Version database artifacts together with the application.
- 02
Separate changes into deployable migration steps.
- 03
Coordinate the database and application views of the same transition.
Keep in mind
The article spans multiple database and deployment contexts. A migration strategy still needs engine-specific lock and performance analysis.
Try this next
Plan a column change as an additive schema step, compatible application change, bounded backfill, verification, and later removal.
Get the data templateNotes and exercises by Awesome CTO. The original work belongs to Pramod Sadalage and Martin Fowler.