Likelihood to Recommend
It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.
Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.
Read full review
Store versions of DB's and Schemas this is useful for every software developer company that works with Databases. Now days al the software use a DB and control those changes are a must. have the power to rollback safe has change the way that we work. This increase speed in development while increase the business confidence.
Read full review Pros Revision control done properly - you have end to end visibility of all changes in the project. Conflict resolution - visually highlighting the differences helps to track down the problem. Being open source and very popular. We are using SVN hosted in our network - it is very stable, we had almost zero downtime in 4 years. Rollbacks are made simple and easy to use. Read full review It can automate database deployment scripts, consistently deploy the same way in every environment, have rollbacks always prepared for every database change, and have all detailed info of deployments in one place Liquibase's changelog files serve as a centralized hub for all database changes. This makes it easy for multiple developers to work on the same project without conflicts, enhancing collaboration and reducing errors Read full review Cons Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists. Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!) Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion. Read full review Reducing Compatibility issues, when we upgraded Liquibase from 4.2 to 4.9. The same changeset which we were able to run on successfully using 4.2, part of it was now failing when tried to deploy using 4.9 We are not able to see detailed logs (for different changes) in uDeploy when deploying changes through Liquibase Liquibase should rollback the if any one of the changes fails. Read full review Likelihood to Renew
While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.
Read full review
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.
Read full review Usability
Build process is too time consuming and getting extra DB instance takes a toll
Read full review Support Rating
Liquibase's customer support is at the top of my list of all vendors I've ever worked with over my 12 years of experience. They work directly with you to be successful, and response time is second to none. Liquibase is committed to getting customers up and running and - more importantly - successful in their organization and becoming champions of the product.
Read full review Implementation Rating
the database deployments helped us with increased productivity,
faster delivery and low risk. Read full review Alternatives Considered Git
has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but
is the future.
Read full review
Liquibase makes it easy to integrate into CI/CD pipelines, keeping the database and code in sync. The switch from one database management system to another is made easier by modeling the structure of the database in DBMS-independent XML rather than SQL. A user-friendly web console gives you a complete picture of the database landscape by showing you which environments have received a particular changeset.
Read full review Return on Investment Subversion helps us feel secure in maintaining access to all of our product code, both current and historical. Being free and open source makes it an even better "investment". Read full review We need to re-educate developers to use Liquibase. In some cases, it is hard to align when several teams work on the same DB. On the other hand, Liquibase provides order and consistency in managing DB changes. Evidence and traceability are a plus. Read full review ScreenShots