role-database:database-migration

Zero-downtime database schema migration uses patterns like expand-contract and blue-green deployments to apply schema changes without service interruption. This approach involves splitting migrations into backward-compatible phases, allowing new and old application versions to run simultaneously during the transition.

Cross-engine database migration from MySQL to PostgreSQL requires translating SQL dialects and migrating schema definitions alongside data. Using tools like Debezium for change data capture or specialized migration scripts ensures data consistency during the transition between different database engines.

Integrating Flyway or Liquibase into CI/CD pipelines automates database schema migrations during deployment. This ensures version-controlled schema changes are applied consistently across environments, using migration tool specifics to validate SQL scripts before production deployment.

The expand-contract pattern is needed for zero-downtime database migrations when applying breaking schema changes. You first expand the schema to support both old and new versions, deploy the application, then contract by removing obsolete columns after confirming the new version is stable.

Prisma Migrate primarily manages schema migrations for applications using the Prisma ORM. For cross-engine database transitions like MongoDB to PostgreSQL, you typically need specialized data replication tools like Debezium combined with custom SQL scripts rather than relying solely on schema migration tools.