We performed a comparison between Git and Liquibase based on real PeerSpot user reviews.
Find out in this report how the two Version Control solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Git is a product everyone uses, so it's almost inescapable. I like the fact that there is a large ecosystem around it. You can bolt various graphical user interfaces onto it or sign up for various repositories like GitHub and AWS CodeCommit. Git has a large community, so there are lots of resources and knowledge bases you can use."
"The most valuable feature of Git is the ease of tracking in time what the snapshot of the code was at a particular moment. The versioning is good."
"Stability-wise, I rate the solution a ten out of ten...Since I am a very simple user of the tool, its scalability is good for me."
"The tool's most valuable feature is branch workflows."
"The most valuable feature of Git is its ability to track updates, such as firmware documentation. Additionally, many people can make changes to code without problems. It is able to solve conflicts very easily."
"The most valuable feature of Git is its reliability and user popularity."
"The implementation is easy."
"Git has a lot of online tutorials and resources available."
"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."
"The solution is easy to use, and it has very clear documentation."
"It will be useful for teams to automate and reduce manual work."
"The tool is complicated for a beginner. You need to have some training to use it. It is also hard to find a parameter."
"More security is always welcome in my opinion."
"It would be preferable if the updates could be completed at a faster pace."
"The scalability could be better. I think it requires some discipline to have large teams working on the same project without facing problems merging code. I'm using Git for personal projects, but I know companies face merge conflicts when more than one person is working on code simultaneously."
"The UI can be more user-friendly."
"It's not very user-friendly."
"The solution could be more user-friendly."
"Git removed the credential feature."
"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."
Earn 20 points
Git is ranked 4th in Version Control with 37 reviews while Liquibase is ranked 7th in Version Control with 3 reviews. Git is rated 8.6, while Liquibase is rated 8.6. The top reviewer of Git writes "A stable solution that can aid its users in maintaining all application developments ". On the other hand, the top reviewer of Liquibase writes "Offers integration with multiple databases, stable product and reduced our manual intervention". Git is most compared with Atlassian SourceTree, Canonical Bazaar, Surround SCM, IBM Rational ClearCase and Bitbucket, whereas Liquibase is most compared with Bitbucket and DBmaestro Database Source Control. See our Git vs. Liquibase report.
See our list of best Version Control vendors.
We monitor all Version Control reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
