Hi, in our team we're using Flyway. The reason we use Flyway is that we are developing on the JVM so it has support for Java, Scala and Groovy (which we are cu

Hi, in our team we're using Flyway. The reason we use Flyway is that we are developing on the JVM so it has support for Java, Scala and Groovy (which we are currently using) and eventually also Kotlin. I suggest to use a version control tool when you are in greenfield projects and your database schema and data might change a lot. Additionally it offers an easy way to control and keep track on how the database evolves. Imagine having to run SQL statements directly on the production environment without a clear way of keeping track of the changes. On top you will have consistent changes that you can roll-out across your dev, qa and prod environments in case you have that set-up. As for how we run it, the migration scripts are part of the project and when we release a new version we apply the migration scripts automatically when the artefact bootstraps.