The second big drawback is speed. There will be more latency in this scenario. How much latency depends upon the environment. If there is RDBMS in the source, AWS Data Migration Service will at worst take around 60 seconds to replicate. That cost needs to be accounted for. Secondarily, many triggering events are leveraged which happen fairly quickly but they do add up. - Source: dev.to / 2 months ago

Amazon Database Migration Service might initially seem like a perfect tool for a smooth and straightforward migration to RDS. However, our overall experience using it turned out to be closer to an open beta product rather than a production-ready tool for dealing with a critical asset of any company, which is its data. Nevertheless, with the extra adjustments, we made it work for almost all our needs. - Source: dev.to / 3 months ago

Does AWS DMS make sense here? Doesn't the aforementioned "snapshot+restore to provisioned and upgrade" method suffice? I wanted to get some opinions before deep diving into the docs for yet another AWS service. Source: 10 months ago

One easy solution is AWS DMS. I use it for on-going CDC replication with custom transforms, but you can use it for simple replication too. Source: about 1 year ago

Https://aws.amazon.com/dms/ Azure Database Migration Service. - Source: Hacker News / about 1 year ago

A Kafka-based data integration platform will be a good fit here. The services can add events to different topics in a broker whenever there is a data update. Kafka consumers corresponding to each of the services can monitor these topics and make updates to the data in real-time. It is also possible to create a unified data store through the same integration platform. Developers can implement a unified store either... - Source: dev.to / almost 2 years ago