Versioned database migrations done right
Day 1
Flyway & Liquibase — Concepts, Configuration & Production Patterns
- Flyway: versioned migrations (V1__, V2__), repeatable migrations (R__), naming conventions
- Flyway Spring Boot integration: auto-run on startup, baseline, repair
- Flyway callbacks: afterMigrate, beforeEachMigrate for validation
- Flyway Teams features: undo migrations, dry runs, batching
- Liquibase: changelog formats — XML, YAML, JSON, SQL
- Changesets: id, author, runOnChange, contexts, labels
- Liquibase Spring Boot integration: liquibase.properties, running on startup
- Liquibase rollback: rollback by count, tag, and date
- Preconditions: conditional changeset execution
- Flyway vs Liquibase: comparison by feature — when to choose which
- Safe migration patterns: addColumn/addIndex before removeColumn, online schema changes
- Multi-tenant migration strategies
- CI/CD integration: running migrations in pipeline before deployment
- Testing migrations: Testcontainers with clean databases per test run
What your team walks away with
Development and DevOps teams who can manage database schema evolution safely — versioned, repeatable, and integrated into their deployment pipeline.
- Set up Flyway or Liquibase with Spring Boot and integrate migrations into the deployment pipeline
- Write safe, reversible migrations that avoid locking and data loss
- Apply multi-environment migration strategies with contexts and labels
- Test migrations automatically against a real database in CI using Testcontainers
Book the Flyway & Liquibase training
A practical one-day course covering both tools — teams leave with the knowledge to choose one and implement it correctly.
Get in touch