The Ultimate Showdown of Database Migration Tools
summary
Compares Liquibase and Flyway by function not hype: Liquibase offers rollback-first Liquibase with declared rollbacks, XML/YAML/JSON/Groovy/Java change sets, checksum tweaks and a built-in diff that generates change logs from schema comparisons; Flyway keeps a strict SQL-first Flyway model with versioned and repeatable migrations (checksum-timestamp trick), Java callbacks, baseline rules and undo migrations only in paid tiers. Live audience voting ends nearly even, so choose Liquibase for flexibility and diffs or Flyway for predictable, minimal SQL workflows.
AI-written summary · about
chapters (20)
- 0:00Database migration tools intro
- 1:28Why migrations are necessary
- 3:39Application-first vs database-first approaches
- 6:30Splitting full names
- 8:15SQL vs Java vs XML vs YAML for migrations
- 12:51Splitting names problems
- 15:01Rollbacks and compatibility
- 17:27Flyway vs Liquibase versioning
- 20:19Baseline migrations
- 21:43Flyway undo migrations
- 23:30Migration file organization
- 24:34Checksums and reliability
- 26:42Learning curves compared
- 28:49Conditional migrations
- 30:39Multi-database support
- 33:49Diff for schema changes
- 35:57Tool configuration options
- 39:57Flyway cherry-picking
- 41:00Schema change approaches
- 42:27Summary and tool vote
related talks
49mThe Ultimate Showdown of Database Migration Tools
45mRewriting History: From Database Versioning Tools to Practice
44mDatabase Change Management
16mVersion Your Databases with Flyway
01h 00mLiquibase Data: Version Control and Collaboration for the Database
52mManaging PostgreSQL changes for the Agile DBA
30mGain confidence in your database changes
35mDatabase migrations without downtime