Liquidbase learner
Use Cases and Deployment Scope
Initially, we were doing manual deployments of DB and version controls of commits and changes were not maintained. By using Liquidbase we were successfully able to schema migration and were able to have version controls as well. We did Liquidbase java based migration using spring boot and Liquidbase library.
Pros
- monitor changes independently instead of using version by which we were able to give support to multiple developers and code branches
- It also help in documented history
- it also provide rollback facility
- it also has ability to work with stored logic
- we can have facility to apply logic based on condition
Cons
- sometimes changelog lock may not be release occasionally
- there should be facility to have a timeout in Liquidbase changeset
- sometime performance issues are also observed when recalculating checksum
Likelihood to Recommend
scenarios where liquidbase is well suited
1. Database change management
2. schema refactoring and evaluation
3. Automated database deployments
4. rollback and rollforward capabilities
