We are aiming to propose a main default suggestion for every problem and therefore have our key-principles. Following KISS we have choosen flywaydb for DB versioning as it is simple and you typically just put your SQL files as you would manually run them on your DB.

A famous alternative to flyway is liquibase that allows some DB abstraction. This is typically not needed as most projects have one supported DB to run on. However, flyway removed some features as support for specific Oracle versions and caused some severe issues to our projects in production forcing them to buy a commercial license. While it is OK for commecial projects to buy a commercial license, it was surprising that an OSS edition removed support in a newer version. In this case several users requested liquibase support. As we do not want to drop and replace flyway with liquibase we should consider adding liquibase as a supported option.

To summarize this story:

• add a config option to toggle to liquibase in our app template.
• extend our DB migration guide to support liquibase