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.
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.
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.
Liquibase is a solution for database change management that automates scripts and integrates with MySQL, MSSQL, and PostgreSQL. It simplifies database syncing, reduces risks, and supports SQL validation while effectively tracking schema updates in DevOps environments.Liquibase offers a robust platform for automating database changes, effectively supporting integration with CI/CD pipelines. Users benefit from its capabilities to manage changesets and changelogs, ensuring controlled rollbacks...
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.
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.
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.
We primarily use the solution to package SQL code that implement a database change request.