We performed a comparison between AWS Database Migration Service and Qlik Replicate based on real PeerSpot user reviews.
Find out in this report how the two Cloud Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The installation is easy."
"The initial setup is very straightforward."
"The most valuable feature of AWS Database Migration Service is it catches all the history changes, such as inset, observe, and delete. It tracks everything."
"The solution is stable and reliable."
"As the solution is on the cloud, we don't have to worry about the maintenance of software."
"The database migration services allow us to do real-time synchronization of on-premise and database to plan out our releases."
"If your infrastructure is already on Amazon, it simply makes the most sense to use a tool officially provided by them as an additional service, rather than having to rely on a third-party solution."
"The most valuable feature of the solution is the one I use for report generation. The security risk is very low."
"It enables us to transform data at the latest stage rather than in ETL loads, so it's more ELT which is one of the advantages. It is also in near real-time, which brings significant advantage for our embedded analytics approach."
"It's very user-friendly when it comes to settings and configuration. It also offers very detailed logging about warnings and errors."
"The most useful functions of Qlik Replicate are the data manipulation to transformations."
"We use Qlik Replicate to change data capture of databases in production environments."
"Qlik Replicate stands out with its cutting-edge technology and its ability to handle diverse data management tasks. This powerful tool allows us to efficiently and swiftly load data into various data stores or destinations, while also enabling easy distribution across different endpoints. A notable feature is its capability to reload data from multiple sources by creating multiple tasks within a brief timeframe of fifteen to twenty minutes. This eliminates the need for manual intervention and ensures quick data loading from different tables."
"The main valuable feature is its real-time change data capture (CDC) capabilities, which process data with minimal latency. There is not much delay. It also performs well with batch-wise data applications."
"A pretty good series of connectors is one of the best features of Qlik Replicate."
"Support has been great."
"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."
"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."
"The product's performance could be a little bit better."
"Whatever solution worked today can not be reused in the next migration."
"The server has limits on how many can connect to the database."
"There is no connectivity to the source database or the target database."
"It's not possible to replicate the QVC files in data analytics."
"In various scenarios, an important consideration is when we encounter issues and Qlik Replicate suggests reloading a specific table. If we face any problems or encounter errors with that table, it becomes necessary to make a change in Qlik Replicate. Performing a full reload every time is not feasible or practical. Instead, we should identify the specific issues and address them without repeating the entire reloading process. Based on this approach, we can investigate and resolve the problem by performing targeted loads from the source itself. This change aligns with my perspective and is something I would like to implement."
"Support for this product is not great. It needs to be improved."
"We would like to see more details in messages about errors with the system."
"The solution's flexibility to work with APIs should also be improved since it is very weak in working with APIs."
"We'd like better connectivity."
"When you remote into it the Qlik Replicate UI a lot of times it just freezes. We set up the EC2, to allow them to go to the server and click on the Replicate icon, it just opens up and just sits there. At that point, we have to go into the EC2 and then reboot the server. This should be fixed, it is frustrating."
"It would be better if the solution’s pricing were more obvious."
More AWS Database Migration Service Pricing and Cost Advice →
AWS Database Migration Service is ranked 2nd in Cloud Data Integration with 26 reviews while Qlik Replicate is ranked 16th in Data Integration with 13 reviews. AWS Database Migration Service is rated 7.8, while Qlik Replicate is rated 8.2. 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 Qlik Replicate writes " Performs well with batch-wise data applications but some features can also be overly dependent on each other". AWS Database Migration Service is most compared with AWS Glue, Oracle GoldenGate, Fivetran, Confluent and Oracle GoldenGate Cloud Service, whereas Qlik Replicate is most compared with Oracle GoldenGate, Qlik Compose, Azure Data Factory, Fivetran and SSIS. See our AWS Database Migration Service vs. Qlik Replicate report.
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.
