TrustRadius: an HG Insights company

Liquibase

Score8.7 out of 10

137 Reviews and Ratings

See a Demo

Contact about Liquibase

Please fill out the form below to get in touch.

Liquibase

Connect with Liquibase

What are you interested in?

Already have an account?

You hereby consent to have TrustRadius share the information supplied on this form with Liquibase so that Liquibase and TrustRadius may contact you in regard to the information requested.

What is Liquibase?

Liquibase is a database change management tool that extends DevOps best practices to the database, helping teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database change management into their process than low performers.

Read more details.

Categories & Use Cases

Videos

Who Buys & Uses Liquibase

Liquibase Reviews

What users are saying about Liquibase.
View all Liquibase reviews

Pros

  • Comprehensive Change Tracking and Versioning
  • Reliable Rollback Capabilities
  • Seamless CI/CD Integration and Automation

Cons

  • Complexity of Rollbacks for Intricate Changes
  • Challenging Error Handling and Reporting
  • Cumbersome Changelog Organization for Large Projects

Ultimate tool for managing database schema changes.

Incentivized
Sahil KhanView profile
Data Analyst in Product Management at Rapidops (501-1000 employees)

Use Cases and Deployment Scope

Liquibase is used in our organization to revise and release database schema changes safer and faster from development stage to production stage. Liquibase automates the database CI/CD pipelines to improve speed, reliability and remove manual code reviews. Liquibase improved developer experience and collaboration within the organization. It is easy to manage and deploy database changes.

Pros

  • Liquibase manages database version very well.
  • Liquibase is faster and safer in releasing database changes from development to production.
  • Liquibase does well in automating the deployment of database changes.

Cons

  • The setup and rollback process can be made easy, as of now it is a bit complex and difficult.
  • Liquibase can improve in performance optimization to reduce execution time.
  • Liquibase can improve their error logging for version mismatches.

Return on Investment

  • Liquibase got rollback capabilities which minimizes downtime and maintain database integrity.
  • Members within a team can collaborate efficiently and effectively on the database changes.
  • Automated deployment reduces the risk of human errors and ensures consistency.

Other Software Used

Jira Software, Engagedly, Atlassian Confluence

Liquibase liquified our problems!

Incentivized
Verified User
Employee in Engineering (5001-10,000 employees)

Use Cases and Deployment Scope

We needed a technical solution that would simplify and streamlined how we managed changes for different types of databases (both SQL and NoSQL), as data flows from and to various sources. In particular it was important that the solution would allow an easier way to rollback in case of problems and that it would put us on track to develop compliance with NoSQL databases

Pros

  • Support for a great variety of databases
  • Good documentation
  • Easy to integrate with existing systems

Cons

  • Customer support could be quicker
  • The user experience in using it has not always been consistent due to the CLI

Return on Investment

  • Safer development due to the possibility of creating a DEV environment, leading to higher confidence with deployments in production
  • Fewer databases errors as they were caught early (either through pre-deployment data quality checks or testing better)
  • Increase version control for databases changes

Other Software Used

PostgreSQL, MySQL, Snowflake

Usability

Liquibase Review

Incentivized
Kunwarpreet Singh
Software Engineering Lead in Engineering at Optum (10,001+ employees)

Use Cases and Deployment Scope

We are currently using Liquibase in our project for handling any database management and version control activity changes on MySQL database server. This involves creating any database user or any other DDL and DML database transactions involving table, index creations along with modifying or altering existing tables/views/indexes. As part of our DevOps automation strategy it is integrated into our CI/CD pipelines using github actions pipeline deployments to manage schema changes across multiple environments from Dev to Stage and then to Prod in a controlled and repeatable way. Liquibase is helping in solving our few business problems that includes reducing any database changes deployment time, human prone errors and manual efforts to add database changes on various environments and helps in tracking all database changes as part of a well defined version control system and Liquibase tracks all the database changes in DATABASELOGCHANGE table it helps in tracking and auditing purposes.

Pros

  • Liquibase allows us to track every change made to the database schema using changelog files (XML, YAML, or SQL) where this change is tracked, auditable, and can be rolled back if needed from DATABASECHANGELOG table which eventually helps in being compliant and trackable which are mandatory in my company as we are part of a healthcare organization.
  • It helps in supporting deploying the same changelog across multiple environments (dev, staging, prod) without any manual intervention from CI/CD github actions pipeline.
  • It helps in comparing two database schemas and generate changelogs automatically to bring one in sync with the other using "Liquibase diffChangeLog" command

Cons

  • diff and diffChangeLog commands are powerfu in Liquibase to make two database schema in sync but can produce noisy or incomplete results, especially when comparing across different database types or versions.
  • If two developers create changes with the same id in different files, Liquibase will throw a conflict even if they’re for different modules, along with this changelog files can become large and difficult to organize.
  • While Liquibase supports rollbacks, they often require manual intervention fgor complex changes for example in data migrations or multi-step schema changes, rollback logic can be hard to write and maintain.
  • Currently liquibase have less integration with IDE's like Intellij or VSCode which makes sometime hard to manage changesets and scripts

Return on Investment

  • By using Liquibase it allows faster deployment cycle across environment where changes are automated and version-controlled, reducing deployment time by up to approx 70%.
  • Improved auditability and compliance where liquibase DATABASECHANGELOG table provide a complete audit trail.
  • Liquibase usage has drastically reduced database downtime with rollback capabilities and pre-deployment validation and helps in preventing bad schema changes from causing outages where in my current project estimated downtime reduction of 30–40%.
  • Observed a 60–70% reduction in production incidents related to schema mismatches or missing migrations.

Alternatives Considered

Redgate Flyway

Other Software Used

Redgate Flyway, DbVisualizer, MySQL Workbench

Liquibase a Great Database Management Tool.

Incentivized
Ashton Judson
Principal Automation Engineer in Engineering at FinQuery (201-500 employees)

Use Cases and Deployment Scope

In developing our application, we use Liquibase to maintain and build our database structures. We use it to apply changes and additions to our database and keep track of the changes being made. Liquibase has allowed us to better maintain control over the evolution of our data structures.

Pros

  • Keeps a change log of all change made.
  • Has the ability to rollback when needed.
  • Easily document changes.

Cons

  • Make it easier to roll back changes.
  • Add a GUI to examine the change logs.
  • Continue the good work.

Return on Investment

  • It has allowed us to develop the application faster and more efficiently.
  • It has made the ability to make changes quickly and efficiently with fewer errors.

Other Software Used

DataGrip, JetBrains Rider

Opensource Liquibase

Incentivized
Verified User
Vice-President in Information Technology (5001-10,000 employees)

Use Cases and Deployment Scope

We have automated our database deployments using open-source Liquibase. Process helped reduce the need for DBA involvement during application releases, and provided the ability to tag and release DB artifacts as app artifacts.

Pros

  • Database change logs
  • Database change sets
  • Rollback
  • Easy integration with build tools
  • contexts

Cons

  • Multi schema automation
  • Stored procedure support
  • PLSQL block support
  • logging

Return on Investment

  • Quicker development of database artifacts
  • Easier tracking of DB changes
  • Easier and quicker rollback if needed
  • DB rollback testing

Other Software Used

ServiceNow DevOps, Splunk Enterprise, Dremio

Liquibase Alternatives

Products similar to Liquibase that may also meet your needs.
View all Liquibase alternatives
DBmaestro Database DevOps Platform
CompareLearn more
Redgate Flyway
CompareLearn more
Redgate SQL Provision
CompareLearn more
Bytebase
CompareLearn more
Atlas Cloud by Ariga
CompareLearn more