Liquibase DB version control made easy
Overall Satisfaction with Liquibase
Liquibase for version control of both Oracle Databases (version 12c to 19c) and Postgres. We are pairing it with Gitlab and our use so far has been leaps and bounds better than any previous solution we have used in the past. Version control on databases is always a pain, but with Liquibase, it has helped our team of over a dozen developers be able to control, validate, and not break each other's work in ways that no other tool has been able to do yet.
Pros
- Amazing Documentation
- Easy integration with existing CI/CD pipelines
- Tags and snapshots make rollback a breeze.
Cons
- for Linux installer, add to the script to add to PATH for executable
- Reduce noise on CLI header and show on verbose flag
- SQL code overwrites by Devs in same packages reduced
- Changelog more clear
- Test and Dev Database Development has improved in quality and adoption
We have multiple Developers without having a dedicated DBA, so many people have part of the DBA hat. Those Developers sometimes would make changes without notifying or fully understanding the change and Liquibase has made it easier to track changes and to revert bad changes. It has also helped change the Database from a monolith into more modular parts as we develop our full version control ecosystem.
- Jenkins, GitHub and Atlassian Bitbucket
None of the products we looked at really focused and had good tools for Database Version control at the level we needed. Our monolith system just does not work well with them. We want to change it from a monolith, but we have to version control it first before really making that change. Gitlab+Liquibase was the best choice for us.
Do you think Liquibase delivers good value for the price?
Yes
Are you happy with Liquibase's feature set?
Yes
Did Liquibase live up to sales and marketing promises?
Yes
Did implementation of Liquibase go as expected?
Yes
Would you buy Liquibase again?
Yes


Comments
Please log in to join the conversation