Liquibase is a database change management tool that helps 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 delivers DevOps for the database. Liquibase value proposition: Liquibase speeds up the development process. The…
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 …
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 …
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 preferred over Flyway if your engineers doesn’t have knowledge in the DDL language used in each database product supported. If you only need to support a single database product and your engineers have the skills I would recommend Flyway instead. Liquibase is …
Both liquibase and Flyway help you deploy database changes associated with new application deployments. They will both help with reducing database administration tasks and ensure reliability of the application service. Comparing Liquibase and Flyway, I found liquibase to be …
Liquibase is head and shoulders better than relying on SQL Compare alone for deployments. I haven't used Flyway, but based on our evaluation, Liquibase seemed to have a lot of functional overlap for considerably less cost. I would recommend the use of GitHub or Bitbucket in …
At the time, Liquibase offered a community version and I think Flyway didn’t. In our case, we did not have any previous experience with any database management tools, so we just went with what was free to try out.
Liquibase is an open-source database-independent library for tracking, managing, and applying database schema changes. It was started in 2006 to allow easier tracking of database changes, especially in an agile software development environment Liquibase is an open-source …
Amazon SimpleDB is a highly available NoSQL data store that offloads the work of database administration. Developers simply store and query data items via web service requests, and Amazon SimpleDB does the rest. Unbound by the strict requirements of a relational, Amazon SimpleDB…
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.
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.
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.
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.