Why Database migrations in NextJS? - Purpose & Use Cases

The Big Idea

What if one small mistake in your database update could break your whole app?

The Scenario

Imagine you have a website with a database, and you need to change the structure, like adding a new column or changing a table. You try to do it by hand, writing SQL commands and running them on each server.

The Problem

Doing this manually is risky and slow. You might forget a step, cause errors, or make the database inconsistent across different environments. It's hard to track what changes were made and when.

The Solution

Database migrations let you write changes as code that runs automatically and safely. They keep track of what's been done, so you can update your database structure step-by-step without mistakes.

Before vs After

✗ Before

ALTER TABLE users ADD COLUMN age INT;
-- Run this manually on each database

✓ After

export async function up(db) {
  await db.schema.alterTable('users', table => {
    table.integer('age')
  })
}
// Migration runs automatically and tracks changes

What It Enables

It makes updating your database easy, safe, and repeatable across all environments.

Real Life Example

When your app adds a new feature that needs extra data, migrations update the database without downtime or errors.

Key Takeaways

Manual database changes are error-prone and hard to track.

Migrations automate and record database updates safely.

This keeps your app's data structure consistent everywhere.