Share your experience using Canonical Bazaar

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.

My main use case for Git is for versioning and controlling and sharing my code.

In a recent Laravel project, I used Git to manage versioning and collaboration by adopting a branching strategy. Specifically, main was for stable releases, and stage for ongoing work and feature branches for isolated changes. Each feature branch was shared through frequent commits and pushed to the remote so that teammates could review the work, run it locally, or continue the development without conflicts. Rebase and track history made collaboration smooth, ensured reproducible builds, and provided a safe rollback if a change introduced issues.

I feel that the best features of Git are its reliable branching model and fast commits. The ability to track every change with a full history and accountability is invaluable.

Git's branching model and change tracking have helped my projects significantly, especially in a recent multi-developer Laravel project where several features were developed in parallel. By isolating each feature on its own branch, the team avoided conflicts and could review work incrementally. When a critical bug appeared in production, Git's history and diff made it easier to identify the exact commit that introduced the issue and rollback safely without disrupting the ongoing development. This combination of isolated branches, clear commit history, and reliable rollback capability kept the project stable while allowing fast iteration.

Git has positively impacted my organization by standardizing collaboration, reducing integration conflicts, and making parallel development far more efficient. The branching model allowed teams to work independently without blocking each other. The clear commit history improved code reviews and accountability.

Git works perfectly as is. The CLI works well with Git, and I don't have any recommendations about it.

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

Git deserves a perfect score because it has been around since the '70s and it works flawlessly all these years. Git's reliable branching model and fast commits stand out along with its stability over time.

I don't think that Git has customer support.

The best advice that I can give is that you have to treat Git as a core part of the development process and not just as a storage tool. This way it leads to cleaner collaboration, safer experimentation, and more predictable releases. I would rate this product a perfect ten.