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. Liquibase value proposition: Liquibase speeds up the development…
In my previous project and organization I have used Flyway for database change management and version control similar to Liquibase which I am currently using. Comparing it with Flyway, Liquibase provides more feature flexibility and enhancements to handle complex workflows with …
None of the products we looked at really focused and had good tools for Database Version control at the level we needed. Our monolith system just does not work well with them. We want to change it from a monolith, but we have to version control it first before really making …
The functionalities in general were very similar, but Liquibase was less intrusive and had a larger community, which made incident resolution more agile without depending on the support of the platform itself.
Liquibase met our needs in a better way, even with the free version alone, then we decided to upgrade our license in order to be able to access policy checks baseline feature
There is no real competitor when it comes to what Liquibase does - at least not at the time we considered it three years ago. It was an easy choice in this regard, but we could have said no to it if it made our workload more difficult. But our proof of concept showed there were …
With Flyway you need to Write rollback scripts manually. With Liquibase we have a lot of customization with to rollback with options such rollback-one-changeset or rollback-one-update.
These other products were for infrastucture as code and not as well-suited for managing database changes; instead Liquibase was more oriented towards it and was easier to pick up its syntax also.
There are many things done differently and in a smoother way when it comes to Liquibase. The CI/CD setup flow is easier. Switching between the different versions on different environments is really easy. The UI of login portal is user friendly and easy to use. Overall, it has a …
Liquibase supports a wide range of database management systems (DBMS) including MySQL, PostgreSQL, Oracle, SQL Server, and more. It is written in Java and offers command-line, XML, YAML, and JSON configurations. where as Alembic is primarily targeted at SQLAlchemy users, which …
We adopted Liquibase to complete our Ci/Cd scenarios. Without Liquibase, DB changes were out to scope in our DevOps scenarios. Log and accountability are more clear now.
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 …
Liquibase is much more powerful compared to Flyway since it is much more flexible in nature. You can apply changes programmatically, works with any kind of database and provides features version controlling database schemas. All these features were missing in Flyway and that's …
To be honest, the option of having a free community plan to start testing in a test environment, followed by taking it in production a few months is a great way to evaluate wether or not to do the subscription based plan.
Liquibase is very well suited for database schema management. It works great for any DDL/DML deployments, changes made to database are easy to manage, track or troubleshoot. It comes with a wide variety of Rollback options. Liquibase Policy checks are a great way to enforce standards around Database code development across organization and prevent any unexpected from being deployed
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.
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.
I gave this rating because I feel their customer support staff have a very good and deep knowledge about the product and they are very helpful when we are stuck on something. The customer support is passionate about their product and they are always ready to help their customer as quickly as possible.
There is no real competitor when it comes to what Liquibase does - at least not at the time we considered it three years ago. It was an easy choice in this regard, but we could have said no to it if it made our workload more difficult. But our proof of concept showed there were easy wins to be had by implementing its software.