database-migrations

Safely apply database schema migrations in production by running `npx prisma migrate deploy` in CI/CD pipelines to apply pending migrations, ensuring versioned changes and reliable rollout across environments.

The best way to rollback a database migration is following enforced Prisma Migrate best practices for reliable rollback strategies, ensuring predictable recovery and safe schema reversion across development, staging, and production environments.

Add a new field to a Prisma schema without causing downtime by applying backward-compatible changes and safe patterns like renames with @map, generating migrations via `npx prisma migrate dev` to prevent production service disruption.

Yes, this database migration approach supports data backfills by providing safe patterns for data migrations alongside schema changes, allowing you to populate new fields and prevent downtime during iterative development and automated deployment.

Use `prisma migrate dev` during iterative development to generate and apply migrations locally, whereas use `prisma migrate deploy` in automated CI/CD deployment to apply pending migrations to staging and production environments safely.