Database migrations are not tough and it's all about how you use the right tools to overcome your most common issues for your on-going database development changes.
Most famous open source tools are:
- https://www.liquibase.org/
- https://flywaydb.org/
- Many more...
So, what to choose and when to use liquibase vs. flyway
- liquibase and flyway has more or less same features, except the flyway uses the SQL as a script whereas liquibase supports SQL, YAML, XML, JSON
- Easier setup and configurations then, flyway; liquibase also easy setup though
- Both flyway and liquibase have tooling and integrations support with your CI/CD tech stack
- Little more configurations with more features you need then, go for liquibase
- liquibase has a lot of databases supported
- liquibase has database versions controlling
- liquibase has undoing the migrations, and doing the diff etc whereas, it's premium in flyway
- smaller teams and many projects then, go flyway
- bigger teams with many projects then go for liquibase as you can have rollback and diff features as all varieties of scripts can be supported
References:
No comments:
Post a Comment