migration-specialist

Zero-downtime schema migration uses an expand-contract pattern: add nullable columns first, backfill data in batches, deploy updated application code, then enforce constraints and remove old fields safely.

The expand-contract pattern expands the schema by adding new nullable columns or tables, migrates data while both old and new structures coexist, and contracts by removing obsolete fields after application traffic shifts entirely to the new schema.

Safe backfills process records in batches within transactions to avoid locking tables. You add the column as nullable, populate existing rows incrementally, verify data integrity, and finally apply the required constraint after all rows are valid.

Feature flags support phased schema rollouts by decoupling deployment from activation. You can deploy migration code and new schema changes behind flags, gradually enable traffic, validate data transforms, and reverse the migration if issues emerge.

Reversible database migrations are needed for production deployments whenever schema evolution or data transformation carries risk of failure. They ensure you can rollback structural changes and restore prior data states during phased rollouts without causing outages.

Running large schema changes and data transforms in a single transaction can cause long table locks and production outages. To avoid this limitation, break transformations into batched transactions and use phased deployment workflows.