Share your experience using Canonical Bazaar

My main use case for Liquibase is because, for our product NormaPro, we have different databases and different data schemas for each of our clients. The database, apart from the table architecture and so on, has a lot of business logic embedded within functions and procedures. Liquibase is our main solution for new client provisioning, for deployments of the entire database architecture and all functions and procedures, to find differences between the different database schemas of our clients, and to apply updates and fixes.

Before having Liquibase, we had no control over the software that was running in each of the clients' schemas. Liquibase has provided us with a quick way to find errors in those clients where functions or procedures were outdated.

Every time we have a deployment for a new client, Liquibase, by working like GitOps for database-related matters, makes deployments and the creation of new schemas enormously easier for us.

The best features that Liquibase has are database engine abstraction, programmable code re-execution, granular deployments with contexts and labels, the automated rollback strategy and, above all, inspection and diff and baseline generation.

The rollback strategy allows us to roll back certain deployments that have gone to production with errors. In such a way that we always have a possible mechanism to roll that step back to the previous version for everything related to functions and procedures and table structure inside the database. What I like most about rollback is that we can define a rollback block directly in XML or YAML and Liquibase understands perfectly where it has to go back.

By minimizing errors, minimizing time, with an incredible cost saving, eliminating database incidents, having a diff inspector against our baseline to know which client schemas are outdated or not up to date, to know what differences there are between the different schemas, this has produced an immense cost saving for us. Before, it was very manual, very tedious work and very prone to errors. I have a metric, I have a KPI on errors produced in the database. These errors have decreased almost to zero since we have been using Liquibase.

The syntax, especially as it is agnostic, is not always 100% transparent. In heavy object management, there should be improvements, and when we have large-scale multitenant environments, the orchestration becomes a bit tedious. But basically, for my use case, it is a tool I recommend 100%.

For object management, the problem is the checksum, which has a very strict and sometimes rigid handling. Even if runOnChange is true, helping stored procedures when the code changes, any minor modification or formatting change should be a bit easier.

Liquibase flawlessly solves provisioning, maintains consistency between dozens of schemas, has database version controls integrated into Git, has enormous reliability in auditing. However, it lacks native multitenant orchestration, it has a lot of rigidity in checksum management with programmable code, and the use of native SQL within XML does not work entirely well. I give it eight out of ten because it is indispensable and unbeatable for guaranteeing consistency and automatic provisioning in our multitenant architecture. I only deduct a couple of points for the lack of native multitenant orchestration and the occasional rigidity of checksums when modifying MySQL functions.

We have been using Liquibase for more than four years.

Liquibase is very stable.

Liquibase adapts very well to our scaling needs. I would rate it a ten.

The documentation is clear, concise, and I can find everything on their website.

We previously used migrations within NodeJS, but when the product started to scale and we had more and more clients and more schemas, the solution did not seem feasible.

Basically, what we launch is a pipeline where all the database changes are provided and Liquibase is responsible for coordinating and controlling all the schemas of all clients to apply the changes to all of them at once.

We have an ISO 27001 certification and within the specifications of the standard, we have change management where there is a specialized team for database changes, basically in charge of coordinating all movement with Liquibase. Only they are the ones who have access to this tool and to put changes into production regarding databases.

The license versus the return on investment that we have had is very substantial.

Liquibase costs us thirty-three dollars a month. Basically, in the past, before having Liquibase, finding any error in any client's database would mean hours and hours of a database expert, which would cost us much more than thirty dollars. Much, much more.

We evaluated other options. We evaluated, for example, Flyway, Redgate, and DBmaestro, but Liquibase convinced us because of the price and the direct functionality we were looking for regarding migrations.

I should not hesitate to recommend Liquibase because if you have an environment like ours, where you run many databases, each one for each client, to maintain consistency with the version that is running, it is an essential tool. Liquibase is great software that makes life and maintenance of client databases easier. I give this product a rating of eight out of ten.

My main use case for GitHub is as a source repository where I'm pushing our code there. Whatever the microservices or the services code we have, we are pushing there. We are running our build and scan there using GitHub Actions, so all those activities I'm doing there.

When we are developing a new software or application, we are managing our source repository on GitHub itself, pushing the code there, cloning from there, and pulling the latest changes from GitHub. So all those activities we are doing from there.

We are using GitHub Actions for deployment purposes. We are using GitHub for the source repository. We also have some checks there for building, such as JUnit testing and other Sonar checks. All those checks we have are covered.

In my experience, the best features GitHub offers are its ease of handling. Whatever things we want, we can easily access them there. There are all the different tabs. We can use Actions, we can use repository, we can use project, we can use activity. So all those things, we can go there. We can check whenever we are pushing any changes, and we can see that commit there. Whenever we are raising the PRs, we can easily get them approved and reviewed by our peers. We can approve that one. We can check when the last time we made any changes on that particular repo. If certain things we don't need, we can revert from there. We can create different branches for there. There are a lot of things in GitHub.

Out of all those features, we find ourselves using all these things daily because once we are working on a new feature, we need to create a new branch for each of the individual features. Then we need to pull the latest source data from there because there are multiple developers working on the same repository. And once we have completed our changes, we need to push there. So all these activities we are using day-to-day.

GitHub is impacting our organization a lot in a positive way because everyone is using it. We are familiar with GitHub and have been using it for the last five to six years in place of GitLab and Bitbucket. This is easier and more stable, having proper maintenance with no downtime.

The accuracy and reliability of GitHub's AI output are great. It is helping day-by-day in our development process. Using AI GitHub Copilot, we are fast-tracked with 50 to 60% help coming from GitHub Copilot itself.

When we were using GitHub, sometimes within a month or two, GitHub is down for some time. Also, it is using SAML authentication, so when we restart our system, if there is an update on our laptop that needs to be restarted, it asks for authentication purposes every time. We need to authenticate using the authenticator app, so that's something I think we can avoid if we are restarting our laptop multiple times in a day. We can have it such that in a day, we can get only one-time authentication.

I chose 9.5 out of 10 because a perfect 10 means addressing the issues I explained earlier. For restarting our laptop multiple times, every time it asks for authentication, even if we restarted it just after five minutes. That is something we can handle better. The UI and all those things are good, but we have been using it for the last four to six years. Sometimes, in a couple of months, we face that some maintenance is going on, so it is not available, and that link also gives a 404. That's why I'm not giving a perfect 10, but it is around nine or 9.5 I can rate.

I have been using GitHub for the last five years.

GitHub is stable in my experience. I have not encountered any major outages or issues.

We are using GitHub for a lot of users, so scalability is great. There are no issues with scalability.

Until now, we haven't faced any issue that required us to connect with customer support. Everything is working fine for the last four to five years, so I have never connected with any customer support, and that's good.

I worked on Bitbucket and GitLab before. These were the solutions we were using, but we are familiar with GitHub and are working a lot on this. All those things are very clear and simple, both from a UI perspective and pricing-wise, which is why we switched to this.

We have seen a return on investment with GitHub. Earlier, when we were using different applications for managing the source repository, we were not familiar with them, and their UI was something different. It was taking time for our team members to understand and develop things. But using GitHub reduces, on average, one to two hours of time daily for making things ready, so it has very good metrics.

Other technical aspects are very good. User experience is also very good. Everything is good for me.

My advice for others looking into using GitHub is that if anyone is going for a source repository to manage their code or anything, they can easily go for GitHub. GitHub Actions and GitHub Copilot are available, and we can manage all those things very easily, so everyone can go with this. I rate this product 9.5 out of 10.