AWS Database Migration Service vs. Redgate Flyway

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

Database Migrations on Java-based solutions. It has one of the best integrations with it as a database migration tool, you can do it with the community edition (no pricing involved) and it works flawlessly with Maven and Gradle. It's not an expensive tool in order to use the next level of features and is worth the money. I would recommend reaching that edition level as the object mapping feature gets really handy. I would not recommend it for any Microsoft-based solution (.Net) as is not compatible at all based on my experience, this is a tool only worth it with Java applications.

Incentivized

• Supports many databases
• Community version uses Apache license
• Widely used, good community support

Incentivized

• GUI could be more user friendly
• Applying patch scripts on a blank DB differs from on a DB with data, so the migration could still fail when all tests passed
• Configurations options could be more flexible / powerful

Incentivized

The problem with a cloud-based tool for migration services is the cloud dependency. You are restricted to use the tool along the Cloud provider. Flyway gives you the freedom to use it in any scenario as long as you are working with a compatible database engine. Even if you are working on-premise and you don't have plans to move to a cloud architecture. Or even for sandbox development scenarios where you are a developer playing around with some project ideas. And you don't have to pay anything as long as you need advanced features, and not less importantly, you are using an open-source tool.

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

• Reduced our effort for release processes.
• Easy to setup - less than 5 minutes.
• Improve reliability of our databases.
• Easy backup and version control.

Incentivized