Liquibase Reviews

My main use case for Liquibase is version control of database schema, automatic migration during application startup, and rollback support. It provides environment consistency and maintains the same database across development, testing, production, or SIT environments. Liquibase is configurable with many databases including PostgreSQL, MySQL, Oracle, and SQL Server. I use Liquibase with Spring Boot applications, which makes it function as a version control system for the database.

A specific example of how I have used Liquibase in one of my projects occurred when we started a project from scratch with new requirements. We had a requirement for a notification table and needed to add new columns to existing tables. I maintained the database schema as a versioned component by writing Liquibase scripts to create a new table and alter an existing table, with each change in separate script files. During application startup, these scripts executed automatically if they had not been executed previously in the database, maintaining consistency. Regarding rollback, when I wrote a script to add an index to a column in a table that passed in the development environment but failed in the QA environment, Liquibase supported rolling back the changes that had been executed in one of the environments.

I use Liquibase daily with Spring Boot applications and microservices, placing the migration files in the application. Liquibase acquires the lock when altering a table to add a new index, so I typically schedule these changes during off-business hours to avoid impacting customers.

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.

I believe the official documentation of Liquibase could be more detailed and comprehensive. Although Liquibase has substantial community support through open source tutorials and Stack Overflow resources where people can find solutions, the documentation could be simpler and more explanatory.

I have continuously used Liquibase for the last four years.

The advice I would give to others looking into using Liquibase is that the initial setup might require some time and extra configuration file changes, but that time investment is worthwhile because Liquibase is very helpful when the database is complex and changes occur frequently.

In terms of features and improvability, Liquibase is the best option in the market to maintain database version control.

Regarding Liquibase's AI capabilities, I think it provides additional solutions for security purposes, but I have not used those features. My use case has focused only on database consistency. For database security and governance, Liquibase keeps production data safe with controlled schema changes and separates duties by designating which changes should occur in development, production, and QA environments.

I have not used Liquibase's AI capabilities.

I did not purchase Liquibase through the Google Cloud Marketplace because it is free and available at no cost. There is no need to purchase a paid plan.

I give this product a rating of nine out of ten.

We are currently not using Liquibase, but we have used it earlier for database deployments. I have provided product information on the PeerSpot site.

Liquibase's valuable features include database deployment and rollback scripts, where we kept our scripts in SQL format. When we deployed using CI/CD, it connected to Liquibase and deployed those scripts to the desired database. We integrated it with CI/CD Jenkins to execute all Liquibase operations, and the logs were retained for around two to three months.

Liquibase's adaptive change scripts benefited our database management process significantly. Previously, if someone logged into the database, they could make changes without any information or change orders. We restricted the DB servers to the DB team specifically. Whenever they wanted to execute changes, they had to go through the change order process, and we would not provide them the password until then. We maintained complete logs so that if any database change occurred and an application stopped working, we had change orders to reference and determine whether it was a legitimate change or a normal variation.

Liquibase's rollback functionality impacted our deployment downtime positively. We would take a backup before anything was executed on the database while we had the change order. Once execution occurred, we performed sanity checks by the application team. If the checks passed, we proceeded. If not, we restored the same copy to avoid database outages.

Liquibase is a very powerful tool in terms of database automation.

I have not found many disadvantages with Liquibase. However, it does not have inbuilt rollback management. You have to take your own backup and restore it if there is any failure. It does not have a feature for rolling back or creating a snapshot of the existing database, so those things must be managed manually.

Liquibase could implement rollback compatibility in the future. Additionally, there were checksum errors, and the logs were not reporting properly in Liquibase, so those issues could be fixed.

I used Liquibase for around two and a half years.

They were helpful. We reached out via email or to their community support, and we received immediate responses.

I can rate their job an 8.5 out of 10.

I changed companies, which is why I stopped using Liquibase. The previous organization was still using Liquibase, and there was no switching of the product. However, I moved to a different organization.

I rate Liquibase a nine out of ten. We used the Community Edition for Liquibase.

We used Liquibase's changelog feature extensively. The changelog contains complete information about all the scripts we executed and presents it as event data.

Liquibase's CLI was powerful. We executed scripts through the CLI, and from CI/CD, we called those commands using the CLI.

We built a separate tool for monitoring the databases where we logged the query speed in terms of Liquibase's tracing and monitoring capabilities helping with compliance for our enterprise. We were not using any inbuilt tool from Liquibase. In terms of compliance and audit, we had the challenge that the compliance team would spend weeks gathering manual evidence for audits. We maintained change orders where we kept the change queries that we were going to execute on the production database from the DBA so that everything would be compliant because of these change orders.

My overall review rating for Liquibase is a nine out of ten.

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.

Liquibase has positively impacted my organization by significantly increasing deployment frequency for database changes. We went from releasing database changes maybe twice a month because they were so manual and nerve-wracking to releasing them as part of every sprint.

I find it hard to put an exact number on how much deployment frequency increased, but the productivity gains are real. The manual database deployment process before involved a DBA, a developer, a change ticket, a scheduled maintenance window, and probably three to four hours of human time.

The best features Liquibase offers include the DATABASECHANGELOG table, which is deceptively simple but is the foundation of everything. Every change that has ever been applied is logged there, including who wrote it, when it ran, which environment, and the checksum.

Having that detailed tracking from Liquibase definitely helps me and my team day-to-day, making troubleshooting or audits easier.

Drift Detection is the other feature I would fight for, as the moment someone makes a manual change to a database outside the pipeline, it shows up. In a regulated environment, that is not just useful, it is necessary.

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 a gap between reading the docs and actually being confident with it.

I would appreciate more sophisticated pipeline analytics out of the box without having to set everything up manually.

I have been using Liquibase for a total of four years.

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 else we evaluated.

Regarding Liquibase's AI capabilities, I think its governance and security are solid.

Regarding Liquibase's AI capabilities, I believe its accuracy and reliability of output could be improved.

We deploy Liquibase using GitHub Actions and Jenkins depending on the client environment. Liquibase itself runs as part of the pipeline job, connects to the target database, applies the pending change sets, and exits. There is no separate server to manage.

My experience with pricing, setup cost, and licensing is that the open-source version is free and genuinely capable for most use cases. We moved to Liquibase Secure for the governance features: audit logs, Drift Detection, policy enforcement, and separation of duties.

My main use case for Liquibase is database versioning and change set management.

A specific example of how I use Liquibase for database versioning and change set management is that it ensures my schemas are versioned instead of losing track of them over time. Liquibase automatically rolls back changes if there are problems during a release, making the process simple.

In addition to my main use case, Liquibase has helped us solve the issue of reverting changes.

The best features Liquibase offers are the schema change sets and the change tracking on any kind of change in the database.

I definitely find that the change tracking feature makes my workflow easier.

Liquibase has positively impacted my organization by eliminating the risk around database changes.

Eliminating that risk has affected my team and business overall by removing costly downtime when trying to revert a problem deploy with a database.

I cannot think of anything at the moment regarding how Liquibase can be improved.

I am uncertain about Liquibase's AI capabilities regarding its governance and security.

I am uncertain about Liquibase's AI capabilities regarding its accuracy and reliability of output.

I have been using Liquibase for 12 years.

Liquibase is stable.

I did not previously use a different solution.

My experience with pricing, setup cost, and licensing is that it is easy since it is open source.

Before choosing Liquibase, I did not evaluate other options.

The advice I would give to others looking into using Liquibase is to make sure you read the documentation. I would rate this product 9 out of 10.

My main use case for Liquibase is database-as-code, which we use for creating table schemas, maintaining migrations, and ensuring that in production, if rollbacks happen, then it's more controlled than running raw SQL.

I can give you a quick specific example of how I've used Liquibase for migration. Although we have not used it for rollbacks until now, we do use it for managing our scripts during migration.

Liquibase is a database-as-code provider, and that is pretty much how we use it.

The best features Liquibase offers include CI/CD integration, which we really appreciate because we didn't have a lot of issues integrating it into our existing CI pipelines, and the changeset and changelog, which are the source of truth that effectively tell us how the database changes are taking effect.

The CI/CD integration helped my workflow by improving visibility with the changelog and changeset. For the CI part, Maven and Gradle builds are already available, so we just use the Maven plugin and it was pretty straightforward.

There is something called Liquibase Validate as well, which helps with pre-deployment checks. We use the update SQL command for dry-run approvals.

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. With Liquibase, you have that history through the changelog and changeset tables, which maintain that history of changes.

Liquibase can be improved by addressing the issue that changelog files could conflict with Git if they're not modularized properly. While we create one file per feature, rollbacks are not magical and require significant consideration, and large diff operations can also be very slow, affecting performance.

We only use MySQL for now, so there's nothing related to any exotic database features, and we're not consuming anything on that side either.

I have been working in my current field for about two years.

My main use case for Liquibase is currently data warehouse deployment.

For data warehouse deployment, we have a product with SQL Server, and we use Liquibase as part of scripts for data warehouse layers with CI/CD based on a copy solution.

Another use case connected with Liquibase is application deployment; it was an application based on Oracle and SQL Server databases, and we use Liquibase as a deployment method for both databases.

The best features Liquibase offers compared to competitors include its flexibility with the options of files that you could use for delivery, such as YAML, XML, and SQL, providing various possibilities to deliver the best script for various deployments.

The flexibility of using different file formats in my day-to-day work can be easier if I use YAML or XML files for applications, which are set up based on various RDBMS; however, for data warehouse, SQL code is more useful because the code is much longer, based only on one database type, and that is why we use SQL for warehousing and XML or YAML file for application deployment.

Liquibase has positively impacted my organization by speeding up the deployment process in the CI/CD framework, being much more useful than different solutions for database deployment that we used before.

While we did not create any KPI for that, we notice it is much quicker, especially in application deployment when we have only two configuration files for various database setups, allowing us to deploy a new version of an application within minutes instead of hours; for data warehousing, we use a lot of variables that enable us to create dynamic stored procedures, making it feasible even without KPIs, as it saves our team from having to recreate code for various environments.

Liquibase contains most of the features that we really need in the project; however, SQL files could be extended by an additional layer of prerequisites since YAML and XML files have that option, and I believe SQL files could also benefit from having more complex prerequisites.

Regarding Liquibase's AI capabilities, I think it is secure due to the lack of SQL injection, and that suffices for that solution.

In terms of Liquibase's AI capabilities, its accuracy and reliability of output is currently very reliable for the solution that we need.

My advice for others looking into using Liquibase is that they should connect it with GitHub actions because it is a really useful solution. I give this review an overall rating of 10.

People automate code-based technologies, but there can be a lack of automation for databases. This tool is used for database automation in DevOps.

It can be integrated with multiple databases like MySQL, MSSQL, and PostgreSQL. The biggest benefit is automating database scripts and manually backing up the database.

It has a rollback capability, but it has not impacted our operations. It's pretty normal. 

It has been improved a lot in terms of automation, but there is still room for improvement.

There is a lot of improvement to be made in terms of automation documentation. This tool is pretty much new for everyone. 

Compared to Jenkins, a CI tool where you integrate your code and run it for quality checks, which has alternative tools like TeamCity, Liquibase is one of the biggest tools for database automation. 

There is documentation available on the website, but it should be improved.

I have been using it for one and a half years.

It is a stable product. 

It is scalable and performs the same if I add more users. Currently, we have around 650 to 850 members.

We are a service-based company working for a large client in the banking sector, so we didn't get a chance to talk with the Liquibase support team.

For the very first time, the initial setup was a medium complex. One thing we faced issues with is that Liquibase does not show the exact error, which added to the complexity.

Suppose it fails with an error. It won't display the exact error on the CI side. For example, if you integrate Liquibase with Jenkins and your database scripts fail due to syntax errors, it won't show the exact error. It's not user-friendly in that aspect.

It will be useful for teams to automate and reduce manual work. It's not only for one specific team; it's across the team.

We saw tangible benefits from using Liquibase in terms of costs and resource savings. 

We reduced our manual intervention by not having to reach out to multiple teams. For example, when executing scripts, we had to reach out to the database team every time we developed a new script to deploy it. 

By using Liquibase, we write the script and compile it. If the build succeeds, we go back to our deployment tool and update our Active Directory so that it will be deployed into the desired environment. This reduces a lot of manual intervention.

The pricing is fair. 

I would recommend using it. To learn Liquibase, one should have some database knowledge. If the person is from a DBA background, they would be able to learn quickly. But if they are from an application or infrastructure role, it's medium complex.

Before getting started, you should thoroughly go through the documentation and follow the latest changes deployed by the Liquibase product team. 

Basically, when using the product, you should be able to understand it and stay updated on the latest releases.

Overall, I would rate the product a nine out of ten. Organizations should have this kind of tool to reduce manual intervention. The one point they could improve on is documentation, which they haven't clarified, and they need to work on that a lot.

I have worked on the Liquibase commands, Liquibase updates, Liquibase storeback, and some basic commands from Liquibase. We were using the Docker image installed from the AWS CI/CD, downloading this Liquibase image, and updating the command from AWS DevOps.

I'm not very into data engineering, but Liquibase is the first tool I have worked on from a data perspective. We were using the SQL server, which our clients found somewhat complex. So, they opted for Liquibase because it is easy. The solution is easy to use, and it has very clear documentation.

We were not able to delete some of the tables because of a security issue.

I have done the POC project with Liquibase for six months.

Whenever we face any issue, we contact the Liquibase support team, who are very supportive and give us quick responses.

The solution's initial setup is easy if we use the Docker version. We have done a POC on our local tool. It was easy to install Liquibase in our local CLI.

Liquibase is an open-source solution. If you are using Liquibase, you need to update its license. I think Liquibase is affordable for our organization.

We were not able to delete some of the tables because of a security issue. We reached out to Liquibase because we thought the issue was from the Liquibase side, but it was from our end. We restarted the security team from our organization, which sorted our issue. My last project was a finance project, and they were relying on Liquibase only for database deployments.

I would recommend the solution to other users. Liquibase is very easy to use if you do CI/CD deployment for the database. The solution's commands and documentation are very easy to understand. The solution is very easy to learn, and I was able to learn it in two weeks. Liquibase is a user-friendly open-source tool.

Overall, I rate the solution a seven out of ten.

We primarily use the solution to package SQL code that implement a database change request.

Liquibase automates actions previously performed manually.  The automate rules engine to pre-validate SQL code is very flexible and powerful.  It integrates well with IBM's UrbanCode Deploy which had already benn using.

There aren't too many products that do what this solution does, which is to group packages of SQL code that implement a database change request. It's a unique product.

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.

Our experience has been very, very positive so far. There's good customer support. It's a product that few offer.

I can't think of any features that are lacking. So far, it's been quite a good solution for us.  And the vendor continues to enhance the product.

We've been using it for about a year. The first half of the year we were running a pilot, testing it, and obtainin client and internal procurement approval. Now it is fully implemented and we are using it within our organization.

The stability is excellent. It's a solid solution. There aren't bugs or glitches. It doesn't crash or freeze.

We've started using it for real in the past few months and we're scaling it now by adding additional CPU cores, and that's easy enough to accomplish. All you've got to do is add CPU cores to scale. It's pretty easy.

As we're just starting to use it now, and we're scaling up now, we will most likely continue to do so in the coming months.

Technical support has been great. They helped us all the way through the initial implementation and have always been very helpful. We're very satisfied with their service. They are always very responsive.

The solution's initial setup was very straightforward. They worked with us the whole time.

Liquibase helped us with the initial implementation. They were with us every step of the way.

Can't fully determine yet.

Conduct a pilot with vendor support to make sure that you understand how you will integrate Liquibase into your existing processes and what the ROI will be on the license investment.

It took us a while to obtain client and internal approval to procure the licenses for us. We did a pilot first for about three months where we didn't have to purchase the license. 

We're partners with Liquibase. We have a close relationship with them and with IBM.

There was a company called Datical that provided a third-party package that integrated with UrbanCode to handle database changes. There's also a Liquibase open source project that provides capabilities like that. Datical just recently changed their company name to Liquibase.

We're using one of the most recent versions of the solution.

I'd warn other companies that it's a transformation of how you do things. You've got to take into account the people aspect of changing their thinking and their processes. Not every organization is as flexible or adaptable as you might think they would be to a new technology change. It really changes a lot of things such as trusting and allowing the tool to do things that you're doing manually now. I'd advise that new users don't forget about the process transformation that has to occur. It's not just the technical transformation, it's a process transformation.

Overall, I'd rate the solution ten out of ten. It's done everything we've needed it to do.

My main use case for Liquibase is syncing different databases. I have an RDS cluster with different databases, and when there is a change in one database, I sync the other databases with the same changes.

I created a Jenkins pipeline with designed workflows. Using that pipeline, if there is a change in one database or multiple DDL or DML changes occur, developers can use the pipeline to make changes directly in one database and sync to other databases.

Liquibase has positively impacted my organization by reducing the time spent syncing databases.

Manual overhead has been significantly reduced, making Liquibase a valuable tool for us.

Liquibase's best features handle all the overhead of syncing. We do not have to plan any DML or DDL changes manually and apply them to the database. It also reduces the risk of inconsistent changes.

Liquibase reduces the risk of inconsistent changes in my experience by syncing the database easily, and there is no manual intervention required.

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.

I have been using Liquibase for more than two years.

Liquibase is overall good software, but for first-time users, it could be more intuitive. Everything else works well. I would rate this review as a six.