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."AWS Database Migration Service is good for smaller workloads and provides compatibility."
"The installation is easy."
"It's scalable."
"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 fact that it's well-integrated into multiple targets that are good for different use cases is pretty good."
"The most valuable features of the AWS Database Migration Service are the ease of migration, beneficial storage system, security, and simple instance creation. Additionally, the cloud that is provided is more complete than other solutions."
"The database migration services allow us to do real-time synchronization of on-premise and database to plan out our releases."
"The solution is instantaneous. We can launch the service and reduce the end number of manpower."
"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."
"Support has been great."
"Great with replicating and updating records."
"The most useful functions of Qlik Replicate are the data manipulation to transformations."
"It's very user-friendly when it comes to settings and configuration. It also offers very detailed logging about warnings and errors."
"A valuable feature of Qlik Replicate is that you do not need ETL. It's easy to use—you choose two systems and it automatically replicates them. Even if there is no CDC available, if you insert it and update it, and there is nothing to find out, then you can use Qlik Replicate. It's a good product."
"From a technical perspective, this is an excellent product."
"Low-priced reporting and analytics solution, with good scalability and stability. It has on-premises and cloud versions that are cohesive and can integrate well."
"This solution is compatible with only AWS."
"Whatever solution worked today can not be reused in the next migration."
"There are a set of complexities and challenges when a user wants to integrate AWS products with Microsoft products."
"It would be helpful if the bandwidth could be independent of the network or if we could have a dedicated bandwidth for this product."
"The way that the task settings work, specifically for logging, is really poor."
"We would like to see some improvement in the performance of large scale procedures, such as when we migrate from Oracle to csSQL."
"The server has limits on how many can connect to the database."
"The names of the services need improvement since AWS doesn't indicate what the function of the product is presently. You need to read a lot to find the service that you want in the product."
"Support-wise, this solution is in need of improvement."
"The UI and data version control can be improved."
"The solution's flexibility to work with APIs should also be improved since it is very weak in working with APIs."
"This product could be improved by providing more insight regarding errors. One of our customers that uses Qlik Replicate has had an issue. We tried to debug it, but we could not trace the error message. The infrastructure site should give us more insight about errors. Qlik Replicate is not a business solution, it's an IT solution. The reporting tools and bug site should be improved."
"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."
"It's not possible to replicate the QVC files in data analytics."
"Support for this product is not great. It needs to be improved."
"We'd like better connectivity."
More AWS Database Migration Service Pricing and Cost Advice →
AWS Database Migration Service is ranked 2nd in Cloud Data Integration with 27 reviews while Qlik Replicate is ranked 17th in Data Integration with 12 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 "A highly stable solution that can be used to change data capture in legacy systems". AWS Database Migration Service is most compared with AWS Glue, Oracle GoldenGate, Fivetran, Confluent and SSIS, 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.
