We performed a comparison between AWS Database Migration Service and CloverETL based on real PeerSpot user reviews.
Find out what your peers are saying about Amazon Web Services (AWS), MuleSoft, Matillion and others in Cloud Data Integration."This solution is very good at mini-batch processing."
"The product's initial setup phase was very easy."
"The initial setup is very straightforward."
"The fact that it's well-integrated into multiple targets that are good for different use cases is pretty good."
"What I like about AWS Database Migration Service is that it's a good product that allows you to migrate terabytes of data. My team was able to migrate almost 16TB of data using AWS Database Migration Service. The solution works fine for my use case."
"I like that I can focus on the logic and I don't have to worry about the administration stuff. AWS handles that for me."
"The process is now simplified because there won't be maintenance. Usually we can take a snapshot of the number I need. We can automate the backup snapshots and we can restore it very quickly. We get many benefits from the application."
"The installation is easy."
"Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility."
"No dependence on native language and ease of use."
"Key features include wealth of pre-defined components; all components are customizable; descriptive logging, especially for error messages."
"Server features for scheduler: It is very easy to schedule jobs and monitor them. The interface is easy to use."
"This solution is compatible with only AWS."
"There are a set of complexities and challenges when a user wants to integrate AWS products with Microsoft products."
"The product's performance could be a little bit better."
"More endpoints need to be supported by AWS Database Migration Service. There's also a need for more control and transparency on the product, including better technical support."
"We would like to see some improvement in the performance of large scale procedures, such as when we migrate from Oracle to csSQL."
"There is no connectivity to the source database or the target database."
"Database Migration Service could be more integrated. I think that it makes sense to add integration to these functions. For example, AWS Glue has a feature called Orchestrator to create data flows, and that's more straightforward."
"AWS Database Migration Service can become complex when testing. Other solutions, such as Microsoft Azure makes it easy to do. There are more steps to complete tasks in AWS Database Migration Service than in Microsoft Azure."
"Resource management: We typically run out of heap space, and even the allocation of high heap space does not seem to be enough."
"Needs: easier automated failure recovery; more, and more intuitive auto-generated/filled-in code for components; easier/more automated sync between CloverETL Designer and CloverETL Server."
"Its documentation could be improved."
More AWS Database Migration Service Pricing and Cost Advice →
Earn 20 points
AWS Database Migration Service is ranked 2nd in Cloud Data Integration with 27 reviews while CloverETL is ranked 60th in Data Integration. AWS Database Migration Service is rated 7.8, while CloverETL is rated 7.0. The top reviewer of AWS Database Migration Service writes "A cloud solution for live replication but has stability issues". On the other hand, the top reviewer of CloverETL writes "Provides wealth of pre-defined, customizable components, and descriptive logging for errors". AWS Database Migration Service is most compared with AWS Glue, Oracle GoldenGate, Qlik Replicate, Fivetran and Confluent, whereas CloverETL is most compared with iWay Universal Adapter Framework and Talend Open Studio.
See our list of best Cloud Data Integration vendors.
We monitor all Cloud Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.