We are currently not using Liquibase, but we have used it earlier for database deployments. I have provided product information on the PeerSpot site.
Liquibase is a solution for database change management that automates scripts and integrates with MySQL, MSSQL, and PostgreSQL. It simplifies database syncing, reduces risks, and supports SQL validation while effectively tracking schema updates in DevOps environments.


| Author info | Rating | Review Summary |
|---|---|---|
| Lead Devops Engineer at a computer software company with 201-500 employees | 4.5 | I found Liquibase very powerful for database automation, with excellent deployment, rollback, and changelog features, improving governance. Despite lacking inbuilt rollback management, it was highly effective, earning a 9/10. |
We are currently not using Liquibase, but we have used it earlier for database deployments. I have provided product information on the PeerSpot site.
Liquibase's valuable features include database deployment and rollback scripts, where we kept our scripts in SQL format. When we deployed using CI/CD, it connected to Liquibase and deployed those scripts to the desired database. We integrated it with CI/CD Jenkins to execute all Liquibase operations, and the logs were retained for around two to three months.
Liquibase's adaptive change scripts benefited our database management process significantly. Previously, if someone logged into the database, they could make changes without any information or change orders. We restricted the DB servers to the DB team specifically. Whenever they wanted to execute changes, they had to go through the change order process, and we would not provide them the password until then. We maintained complete logs so that if any database change occurred and an application stopped working, we had change orders to reference and determine whether it was a legitimate change or a normal variation.
Liquibase's rollback functionality impacted our deployment downtime positively. We would take a backup before anything was executed on the database while we had the change order. Once execution occurred, we performed sanity checks by the application team. If the checks passed, we proceeded. If not, we restored the same copy to avoid database outages.
Liquibase is a very powerful tool in terms of database automation.
I have not found many disadvantages with Liquibase. However, it does not have inbuilt rollback management. You have to take your own backup and restore it if there is any failure. It does not have a feature for rolling back or creating a snapshot of the existing database, so those things must be managed manually.
Liquibase could implement rollback compatibility in the future. Additionally, there were checksum errors, and the logs were not reporting properly in Liquibase, so those issues could be fixed.
I used Liquibase for around two and a half years.
They were helpful. We reached out via email or to their community support, and we received immediate responses.
I can rate their job an 8.5 out of 10.
I changed companies, which is why I stopped using Liquibase. The previous organization was still using Liquibase, and there was no switching of the product. However, I moved to a different organization.
I rate Liquibase a nine out of ten. We used the Community Edition for Liquibase.
We used Liquibase's changelog feature extensively. The changelog contains complete information about all the scripts we executed and presents it as event data.
Liquibase's CLI was powerful. We executed scripts through the CLI, and from CI/CD, we called those commands using the CLI.
We built a separate tool for monitoring the databases where we logged the query speed in terms of Liquibase's tracing and monitoring capabilities helping with compliance for our enterprise. We were not using any inbuilt tool from Liquibase. In terms of compliance and audit, we had the challenge that the compliance team would spend weeks gathering manual evidence for audits. We maintained change orders where we kept the change queries that we were going to execute on the production database from the DBA so that everything would be compliant because of these change orders.
My overall review rating for Liquibase is a nine out of ten.
| Product | Mindshare (%) |
|---|---|
| Liquibase | 4.7% |
| Git | 18.1% |
| Bitbucket | 11.8% |
| Other | 65.4% |
| Company Size | Count |
|---|---|
| Small Business | 3 |
| Midsize Enterprise | 3 |
| Large Enterprise | 3 |
| Company Size | Count |
|---|---|
| Small Business | 38 |
| Midsize Enterprise | 20 |
| Large Enterprise | 94 |
Liquibase offers a robust platform for automating database changes, effectively supporting integration with CI/CD pipelines. Users benefit from its capabilities to manage changesets and changelogs, ensuring controlled rollbacks and pre-deployment checks. Liquibase is highly valuable for managing database-as-code tasks like schema creation and maintaining migrations. Despite its strengths, areas like security, documentation on automation, and performance during diff operations, especially in large-scale situations, could see improvements. Integration challenges with Git, particularly with changelog file conflicts, are noted by users who also seek an enhanced newcomer experience.
What are Liquibase's Most Important Features?In DevOps environments, Liquibase is crucial for automating database changes and ensuring migrations are consistent across various platforms. Financial institutions and e-commerce companies frequently implement Liquibase to synchronize multiple databases via Jenkins pipelines, promoting reliable change management and operational efficiency.
Nike, JP Morgan Chase, Bancolombia, UPS, Anthem