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.
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.
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 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.
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.
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.