Course contentsShow
← Software Engineering
Lesson 721 of 1,93322. Continuous Delivery and DeploymentFree lesson

Database Rollbacks and Schema Compatibility

Forward-compatible migrations, separating schema from data changes, and handling database rollbacks safely.

Database Rollbacks and Schema Compatibility

You'll learn how to design database migrations that can be safely rolled back without breaking your application or losing data.


When a deployment fails, rolling back application code is straightforward—just redeploy the previous version. But databases are stateful: rolling back a schema change that deleted a column or renamed a table can cause data loss or application crashes.

The Core Challenge

Imagine you deploy version 2 of your app that expects a user_email column, having migrated from email. If you rollback the app to version 1 (which expects email), it will break because the old column is gone. Schema changes must be compatible with both the old and new application code.

Forward-Compatible Migrations

Design migrations that work with multiple versions of your application simultaneously:

Additive changes are safe:

  • Adding new columns (with defaults)
  • Adding new tables
  • Adding indexes

Breaking changes require multiple steps: Instead of renaming email to user_email in one deployment:

  1. Deploy 1: Add user_email column, write to both columns
  2. Deploy 2: Migrate old data, read from user_email
  3. Deploy 3: Remove old email column

Each step is independently rollback-safe.

Separating Schema from Data

Run structural changes (ADD COLUMN) separately from data migrations (UPDATE statements). If a rollback occurs mid-data-migration, your schema remains intact and the app continues functioning—you just retry the data update later.

Handling Database Rollbacks Safely

  • Never drop columns immediately after a deploy
  • Keep old and new schemas working simultaneously for at least one deployment cycle
  • Use database transactions for data migrations when possible
  • Test rollback scenarios in staging environments

Key Takeaway: Safe database rollbacks require forward-compatible schemas where changes support both the previous and current application versions, enabling you to rollback code without breaking database compatibility.