No more typing reviews! Try our Samantha, our new voice AI agent.

Git vs Liquibase comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Aug 14, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Git
Ranking in Version Control
4th
Average Rating
8.6
Reviews Sentiment
7.1
Number of Reviews
38
Ranking in other categories
No ranking in other categories
Liquibase
Ranking in Version Control
7th
Average Rating
8.4
Reviews Sentiment
4.2
Number of Reviews
8
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Version Control category, the mindshare of Git is 13.4%, up from 8.2% compared to the previous year. The mindshare of Liquibase is 5.0%, up from 2.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Version Control Mindshare Distribution
ProductMindshare (%)
Git13.4%
Liquibase5.0%
Other81.6%
Version Control
 

Featured Reviews

Hari Kathireshan - PeerSpot reviewer
Sr PHP Developer at GE
An easy-to-use solution that can be used for configuration management
We use Git for configuration management Git is an easy-to-use solution that can be used for parallel working. Git's user interface could be improved. I have been using Git for almost eight years. Git is a stable solution. Git is a scalable solution. Around 2,000 users use the solution in our…
Akashkhurana Hirana - PeerSpot reviewer
Senior Software Engineer II at Porch.com, Inc.
Daily database version control has ensured consistent schemas and confident rollbacks
The best features Liquibase offers include the database rollback mechanism, open source availability at no cost, and the ability to connect to all relational databases including MySQL, SQL Server, and PostgreSQL. Liquibase provides a rollback mechanism, transaction and lock management, database version control, and change tracking. It maintains a history table in one of the schemas that records which changes have been applied and which changes remain pending. If I need to migrate from PostgreSQL to MySQL in the future, I only need to change the URL and credentials without modifying the database structure, as Liquibase handles everything automatically. Liquibase has a vast community with widespread usage, particularly with Spring Boot microservices applications. Out of all these features, I rely most on database version control in my daily work to maintain a history of when I added columns or tables. The rollback support is excellent and maintains consistency across all environments including development, staging, and production. Liquibase provides a feature to check database differences across multiple environments in QA, development, and production. I can easily compare databases or changes between development and QA environments using this feature. Liquibase integrates easily with CI/CD tools including Jenkins, GitHub Actions, and GitLab with extensive support for these integrations. Liquibase has positively impacted my organization by maintaining database consistency across all environments. Inconsistent databases increase debugging time for engineers and associated costs, and can impact users. The primary benefit Liquibase provides is database consistency, ensuring a consistent database across all environments.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Git has a lot of online tutorials and resources available."
"Git is a stable solution. Stability-wise, I rate the solution a ten out of ten."
"Code versioning, for example, we work in the branch and want to come back to this branch another time.Git is a very useful tool, helpful to collaborate with other members in the group to finish more rapidly our work."
"The repository management and check-in/check-out commands are the most valuable features for ensuring secure code."
"All of the features in Git are useful."
"Git is easy to use."
"The scalability of the solution is good."
"The setup process is pretty simple."
"It will be useful for teams to automate and reduce manual work."
"The solution is easy to use, and it has very clear documentation."
"Liquibase has positively impacted my organization by providing a way to manage database migrations instead of maintaining raw SQL, which comes with the issue of not being able to track certain schema updates or new table creations."
"Liquibase has positively impacted my organization by eliminating the risk around database changes."
"Liquibase has positively impacted my organization by reducing the time spent syncing databases."
"Liquibase has positively impacted my organization by significantly increasing deployment frequency for database changes."
"Our experience has been very, very positive so far."
"They have some nice features around the automation of rule checking. They have a rules engine that checks the SQL code so that you can actually do your edit checks on the validity of the SQL code. If you don't want certain tables to be able to have certain things done to them, you can have it checked for that. It's a very flexible way to kind of do an automated peer review of the SQL code to catch things before you actually try to deploy it."
 

Cons

"I would like to see an improvement in the way the product owner can review changes and so forth."
"The tool's user interface is terrible. It needs to be more user-friendly."
"Git removed the credential feature."
"The main problem for me is the frequent upgrades in the solution because every other upgrade is a minefield. When you do the upgrade, there is always something that doesn't work."
"Git's user interface could be improved."
"Some challenges arise when Git is not used correctly, particularly in managing branches. It's easy to get lost, but these challenges can be overcome with proper management. A common advice is maintaining the repository and ensuring developers are in sync with the production branch. Branches should be promptly merged into development to avoid getting lost in many branches."
"I would rate the initial setup process a four, on a scale from one to 10, with one being the most difficult and 10 being the easiest. The reason for this rating is that once there are conflicts, it takes a lot of effort to resolve them."
"The platform could have a feature for monitoring data recovery similar to Azure."
"I believe the official documentation of Liquibase could be more detailed and comprehensive."
"Liquibase could be improved in several ways. Some facilities could be enhanced, and for first-time users, it could be more intuitive rather than overwhelming."
"Liquibase can be improved by addressing the issue that changelog files could conflict with Git if they're not modularized properly."
"Regarding Liquibase's AI capabilities, I believe its accuracy and reliability of output could be improved."
"We were not able to delete some of the tables because of a security issue."
"One thing we faced issues with is that Liquibase does not show the exact error, which added to the complexity."
"The pricing is quite high."
 

Pricing and Cost Advice

"The tool is free."
"The tool is an open-source product."
"We are using the open-source version, which is available free of charge."
"As a student, I didn't have to pay for the license."
"This is an open-source solution, so there are no licensing fees associated with it, and no extra, 'hidden' charges."
"There are some extra costs to Git, but it depends on your use case."
"The platform is less expensive."
"Git is free and you don't have to pay for it."
"Liquibase is an open-source solution."
"The pricing is fair."
report
Use our free recommendation engine to learn which Version Control solutions are best for your needs.
902,270 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
17%
Financial Services Firm
12%
Marketing Services Firm
10%
Construction Company
8%
Financial Services Firm
22%
Manufacturing Company
13%
Computer Software Company
10%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business12
Midsize Enterprise9
Large Enterprise21
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise2
Large Enterprise3
 

Questions from the Community

What needs improvement with Git?
There is nothing that could be improved at this time.
What is your primary use case for Git?
I use Git to store our code and maintain different versions, and for some projects, we use CI/CD as part of GitHub.
What advice do you have for others considering Git?
I would recommend Git to other people. I'd rate it nine out of ten.
What needs improvement with Liquibase?
Liquibase can be improved by helping developers who have never used it before to understand change logs, change sets, contexts, and labels, which takes time. The documentation is good, but there is...
What is your primary use case for Liquibase?
My main use case for Liquibase is database change management inside our CI/CD pipelines. Before Liquibase, someone would have to manually run SQL scripts against the database and hope for the best.
What advice do you have for others considering Liquibase?
On a scale of one to ten, I rate Liquibase overall as an eight. I rate it an eight because it fundamentally solved the problem that was genuinely painful and had not been solved well by anything el...
 

Comparisons

 

Overview

 

Sample Customers

Google, Facebook, Microsoft, Twitter, LinkedIn, Netflix, PostgreSQL, Android, Rails, QT, Gnome, Eclipse
Nike, JP Morgan Chase, Bancolombia, UPS, Anthem
Find out what your peers are saying about Git vs. Liquibase and other solutions. Updated: June 2026.
902,270 professionals have used our research since 2012.