mediumBackend

How do you manage database schema migrations in a Node.js project?

Q: How do you manage database schema migrations in a Node.js project?

**TL;DR.** Migrations are **versioned, ordered scripts** (via Prisma Migrate, Knex, or node-pg-migrate) that evolve the schema **reproducibly** across environments. A migrations table records which have run, so each deploy applies only **new** ones. Use **backward-compatible "expand then contract"** steps for **zero-downtime** deploys. 001_init 002_add_col <text class

675 views

Understand the problem

Versioned, ordered schema changes with up/down steps.

nodejsdatabasemigrationsschema

Attempt it yourself

Sketch your approach before reading the solution — that's what interviews test.

Stuck? AI Nudge Available

Get a conceptual hint to guide your logic without spoiling the final implementation.

Study the solution

The solution is waiting

Give it an honest attempt first — then compare your thinking with the full walkthrough.

Read the code

Prisma migration flow

# edit schema.prisma, then create + apply a migration in dev:
npx prisma migrate dev --name add_user_status

# in CI/CD / production, apply pending migrations only:
npx prisma migrate deploy

# Zero-downtime: add nullable column first, backfill, then enforce NOT NULL later.

Join the discussion

Discussion (0)

No responses yet. Be the first to share what you think.

How do you implement retries with exponential backoff and jitter?

How do you handle errors in Node.js applications?