Liquibase maximizes development team with faster deployment
Updated July 01, 2023
Liquibase maximizes development team with faster deployment
Score 10 out of 10
Vetted Review
Verified User
Software Version
Liquibase Pro
Overall Satisfaction with Liquibase
An ease of error-prone and quick database deployments both on-prem and on cloud integrated with CI/CD DevOps Automation.
- Difference of Schemas between two databases
- Baseline on a newer target deployment
- Well fit in with dockers and Azure Devops for CI/CD Automation Deployment
- Snapshots being a great feature on offline diff but need to come up with strong reliability outcome
- Sequences And Unique Constraints outcome from diff changelog is redundant
- More reliability of diff changelog
- Close security integration with DBMSs for database deployment
Once a pipeline/platform is laid out as part of heavy lifting by DBA/DevOps and ownership moved to Development team, DBA deployment efforts/hours have really been subsided.
We like stateless deployment and it helps us.
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
Using Liquibase
30 - Database Deployment using CI/CD
20 - DevOps , DBA And Application Development team.
- database deployment
- application development speed up
- adhoc data patch
- dockerized based database deployment
- schema compare and review
- azure devops ci/cd integrated
- cloud database deployment
- move away from Microsoft Database Project
Evaluating Liquibase and Competitors
Yes - dbforge is state based.
dbmaestro requires additional infrastructure needs as opposed to dockerized using liquibase.
dbmaestro requires additional infrastructure needs as opposed to dockerized using liquibase.
- Cloud Solutions
- Integration with Other Systems
- Ease of Use
the database deployments with increased productivity,
faster delivery and low risk. heteregneous clod database targets deployment.
faster delivery and low risk. heteregneous clod database targets deployment.
we're already on-board with Liquibase with several application development teams
Liquibase Implementation
- Implemented in-house
Yes - application team ensures artifacts. dba laid down the ci/cd pipeline using azure devops
Change management was a small part of the implementation and was well-handled - App team has ensure single source of truth as TFS for database schema to help us use the pipeline for database deployment.
- not an issue but insist on maintaining tfs code inventory as single source of truth for artifacts
Liquibase Support
Application team needs full scale database compare for which we procure enterprise license.
Yes - unique constraints are recreated with 4.17, have to retry with newer release...
sequences owned by table are reported but we do have alternatives adhoc implementations to overcome
sequences owned by table are reported but we do have alternatives adhoc implementations to overcome
Liquibase support team is proactive and prompt response for their customers and we reached out 3 times and they have resolved and addressed our concerns.
| Pros | Cons |
|---|---|
Quick Resolution Knowledgeable team Problems get solved Kept well informed No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response | Poor followup |
Using Liquibase
| Pros | Cons |
|---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Quick to learn Convenient Feel confident using | Lots to learn |
- generatechangelog for rever enginering
- diffchangelog for differential between two databases
- usage of context for variations in the scripts for changeset apply
- snapshots are very useful but snapshot compare needs attention