Liquibase :- If you are not using it, You are missing a big feature
February 28, 2022

Liquibase :- If you are not using it, You are missing a big feature

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Software Version


Overall Satisfaction with Liquibase

We use Liquibase to automate our database deployment in our product offering stack. Before Liquibase this job was done by DBAs to execute scripts on different environments manually which involves human error and delay in getting work done.
  • Automation of execution of database scripts
  • Maintain rollbacks which make it easier in case of any need in rollback
  • Database independent scripts makes it more re-usable
  • Pre-bundle scripts with Gradle, ant with specific target already written
  • A fancy GUI to generate reports on current state of database
  • A GUI/other ways to generate database level reports like ER diagram
  • Positive :- Less error as the process is automated
  • Positive :- Multi database support in a single effort
  • Negative :- Initial learning investment of Liquibase
The DBAs now can fully focused on more meaningful task rather than doing a manual script execution job. They can focus on real challenges like tuning database performance, optimizing queries, etc.
Not only I use Slack and other channels to get help, but I am currently offering help to other users as well. The community is well established and very helpful. The frequent meetup also happens and you can raise any concern or suggest anything with Liquibase people. In summary, community is very active and helpful.

Do you think Liquibase delivers good value for the price?


Are you happy with Liquibase's feature set?


Did Liquibase live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Liquibase go as expected?


Would you buy Liquibase again?


We are using Liquibase since last 4 years now, it has not only reduced the manual efforts but also helped us in saving cost and any human error that may occur. The CICD processes are now well settled and there is 0 manual intervention required to deploy our code base including database from one environment to another.

Using Liquibase

300 - Our entire team of IT people uses Liquibase, the list includes developers till senior managers.
300 - All people working have enough knowledge gain through experience and each one can support other person in case of any need. No special role defined to support.
  • 0 Touch deployment
  • Rollback automation in case of failure
  • Automation through CICD
  • Integrated in developer CICD, making sure rollbacks are also executed and tested before merging into actual branch.
  • Rollback script generation and storing for each new upgrade.
  • Generate DB level reports like ER diagrams etc
We are and will continue using Liquibase and it has become an integral part of our portfolio offering, any new product is by default adopting Liquibase stack.