Liquidbase learner
Overall Satisfaction with Liquibase
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
- reduced database team workload for deployment by 80% as it is automated
- reduced SLA for database deployment with QA by 90 %
- created automated database deployment pipelines to increase productivity
- also reduced operating expenses for new applications
By using Liquidbase we significantly reduce the manual workload of a database administrator by automating database schema change management. so that now administrator is allow to focus on more strategic task like performance optimization , data governance and security.
flyway use sql for defining change but Liquidbase provides flexibility to specify change in different formats including sql such as xml, yaml and json
Do you think Liquibase delivers good value for the price?
Yes
Are you happy with Liquibase's feature set?
Yes
Did Liquibase live up to sales and marketing promises?
Yes
Did implementation of Liquibase go as expected?
Yes
Would you buy Liquibase again?
Yes


Comments
Please log in to join the conversation