Why Blue-Green Deployments Can't Save You From a Bad Database Migration

A software team experienced a full outage when a database migration dropped and recreated a column in a single step, breaking both environments in a blue-green deployment. Because both blue and green stacks share the same database, running the migration before the router flip left the old app code querying a column that no longer existed. Unlike application code, schema changes are not atomic or easily reversible — dropping a column permanently destroys its data, making a simple rollback impossible. The incident highlights a critical distinction between reversible schema changes, such as adding a nullable column, and irreversible data changes like dropping or backfilling columns. Engineers are advised to spread such migrations across three separate releases — expand, backfill, then contract — to ensure safe rollback at every stage.