The Myth of the Maintenance Window
In global 24/7 commerce, the concept of a scheduled Sunday 2 AM maintenance outage is obsolete. Cross-border payments, logistics dispatchers, and mobile users expect sub-second responsiveness around the clock. Engineering teams must adopt migration patterns that accommodate live relational schema changes under active read/write loads.
The Expand-and-Contract Architecture
Every database modification is broken down into four non-breaking deployment phases: (1) Expand: add the new column or table without removing the old one; (2) Dual-write: update the application layer to write to both representations; (3) Backfill: run background workers to populate historical data; and (4) Contract: deprecate the old structure only after all services read from the new structure.
"If a database migration requires downtime, the architecture has coupled schema evolution with release velocity. Decoupling them is the foundation of high-availability engineering."