Amazon EMR VS AWS Database Migration Service

There are different ways to implement parallel dataflows, such as using parallel data processing frameworks like Apache Hadoop, Apache Spark, and Apache Flink, or using cloud-based services like Amazon EMR and Google Cloud Dataflow. It is also possible to use parallel dataflow frameworks to handle big data and distributed computing, like Apache Nifi and Apache Kafka. Source: about 1 year ago

I'm going to guess you want something like EMR. Which can take large data sets segment it across multiple executors and coalesce the data back into a final dataset. Source: almost 2 years ago

This is exactly the kind of workload EMR was made for, you can even run it serverless nowadays. Athena might be a viable option as well. Source: almost 2 years ago

Apache Spark is one of the most actively developed open-source projects in big data. The following code examples require that you have Spark set up and can execute Python code using the PySpark library. The examples also require that you have your data in Amazon S3 (Simple Storage Service). All this is set up on AWS EMR (Elastic MapReduce). - Source: dev.to / over 2 years ago

Check out https://aws.amazon.com/emr/. Source: about 2 years ago

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 / about 1 month 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 / about 2 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: 9 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