Database Migrations Without Fear

What a migration actually is (git for your schema), the golden pattern for changing live data safely, and the dangerous migrations that lock tables or break the running app - so you can change a production schema without losing data or taking downtime.

1. What a Migration Is A migration is a versioned, ordered change to your schema - checked into source control and applied the same way in every environment, like git for your database structure - usually with an 'up' that applies it and a 'down' that rolls it back.
2. Doing It Safely on Live Data The golden pattern for live schema changes: add new structure first, backfill the data, then switch the app over - and the expand/contract (parallel-change) approach that keeps the running app working through a rename or type change with zero downtime.
3. The Dangerous Migrations The migrations that bite: long locks on big tables that freeze writes for minutes, dropping or renaming columns the running app still uses, and non-nullable columns without defaults - plus always having a rollback plan and a real backup before you run anything destructive.