AWS Database Migration Service vs. Liquibase

As stated previously, AWS Database Migration Service excels when replicating very specific data elements between environments. AWS Database Migration Service handles replication tasks to load equipment assets or customer job sites from production to QA databases very well. Full load replication - e.g., we need an exact copy of the production database in another region - works well. But when we need to load the QA database with the latest production data - it does work as well. AWS Database Migration Service comes up short because we do not want to wipe the QA database completely and make an exact copy. We want to keep what's already in the QA database and add production data so that we can QA with that level of volume. And at least with our database design, we end up having to do a lot of manual data manipulation and de-duplication.

Incentivized

Any Codebase that does schema or table changes all the time for development or where Development and code is mostly in the database or SQL liquibase is a must. In a codebase where the database is pretty static or is just a place to dump data, liquibase is probably too much. You also need to have a team for it to really make sense. Doing a solo or small team project doing full version control on the database is probably more overhead than it is worth.

Incentivized

• Liquibase provides a clear error log that allows us to pinpoint what to troubleshoot.
• The service does not deploy bad data, which helps us keep our databases clean.
• Liquibase works with GitHub Actions as well as AWS Codebuild and AWS Lambda. The flexibility allows us to deploy the service in many different ways.

Incentivized

• Reducing Compatibility issues, when we upgraded Liquibase from 4.2 to 4.9. The same changeset which we were able to run on successfully using 4.2, part of it was now failing when tried to deploy using 4.9
• We are not able to see detailed logs (for different changes) in uDeploy when deploying changes through Liquibase
• Liquibase should rollback the if any one of the changes fails.

Incentivized

We are and will continue using Liquibase and it has become an integral part of our portfolio offering, any new product is by default adopting Liquibase stack.

Incentivized

the database deployments helped teams with a increased productivity,
faster delivery and low risk.

Incentivized

Liquibase's customer support team has been very instrumental in helping us drive the whole Database CI/CD initiative. We have always received very quick resolution to our queries or any roadblock we hit. Right from setting up Liquibase in our environment to this date the Liquibase team has always helped us deliver quality and innovative solutions.

Incentivized

Build process takes a toll.

Incentivized

In my previous project and organization I have used Flyway for database change management and version control similar to Liquibase which I am currently using. Comparing it with Flyway, Liquibase provides more feature flexibility and enhancements to handle complex workflows with rollback capability and its usage of contexts and labels allow us to target changes to specific environments, which Flyway doesn’t support natively. Also Liquibase provides way to compare different schema and generate changelogs for syncing environments automatically where in it allows to have declarative schema management by using XML/YAML/SQL script format.

Incentivized

• Set it and forget it for maintaining data consistency - moderate cost, zero to minimal maintenance
• High touch production data loads into QA - negative ROI engineering time investment far exceeded our predictions

Incentivized

• We are still in the early phases, where the costs are potentially greater than the benefit. Trying to get Liquibase integrated into a pipeline has taken time investment and required some trial and error.
• We are still a relatively small shop with a relatively small number of schema changes (perhaps 1 every week or so). As such, we aren't at a place where we couldn't have managed control of this without a tool. However, there is no doubt that investing in a tool at this stage was the right move. Now we have established guidelines and a pattern for how to do schema changes in a way that will make things easily scalable as we continue to grow.

Incentivized