Database Migration Deployment Pattern

Overview

Deploy database-backed services to Kubernetes using the Migration Job + Init Container pattern. This ensures database migrations complete successfully before application pods start, preventing schema mismatches and data corruption.

When to Use

Use this pattern when:

• Service requires database schema migrations before startup
• Deploying to Kubernetes with FluxCD
• Using Prisma, Alembic, Liquibase, or similar migration tools
• Running multiple replicas (horizontal scaling)
• Need atomic, fail-fast deployments

Don't use when:

• Database is external/managed and migrations run separately
• Using schema-less databases (Redis, MongoDB without schemas)
• Application handles migrations internally with locking