We performed a comparison between AWS Database Migration Service and Qlik Compose 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 solution is instantaneous. We can launch the service and reduce the end number of manpower."
"As the solution is on the cloud, we don't have to worry about the maintenance of software."
"For our simple requirement of migration, DMS is just a typical AWS RDS with an IPSec tunnel to Oracle. The most valuable features for us are the networking capabilities like VPCs and VPNs."
"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 product's initial setup phase was very easy."
"The initial setup is very straightforward."
"The Schema Conversion Tool helps to covert the convertible objects and define the non-convertible objects"
"It's scalable."
"I have found it to be a very good, stable, and strong product."
"One of the most valuable features of this tool is its automation capabilities, allowing us to design the warehouse in an automated manner. Additionally, we can generate Data Lifecycle Policies (DLP) reports and efficiently implement updates and best practices based on proven design patterns."
"As long as you pick the solution that best fits with your requirements, you won't find that performance is a problem. It's good."
"It can scale."
"It's a stable solution."
"The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities."
"The technical support is very good. I rate the technical support a ten out of ten."
"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."
"Support could be more expedient. Right now I am waiting on support for an extension."
"Whatever solution worked today can not be reused in the next migration."
"Migrating from here and pushing the data from on-premise to AWS cloud is a big challenge and a few more services from AWS would be helpful. For example, we are currently using ILDB internet tools which move data from on-premise to the AWS cloud. A few more services would be really helpful for me to move the master data."
"The solution’s scalability and performance could be improved."
"What needs improvement in AWS Database Migration Service is that it lacks a log file validation feature. If the solution could provide more details about a particular transaction, that would be helpful. The stability of AWS Database Migration Service for online CDC records also needs to be improved."
"The server has limits on how many can connect to the database."
"There is no connectivity to the source database or the target database."
"The cost is a concern. We use DMS because of its simplicity, but the price could definitely be more competitive."
"For more complex work, we are not using Qlik Compose because it cannot handle very high volumes at the moment. It needs the same batching capabilities that other ETL tools have. We can't batch the data into small chunks when transforming large amounts of data. It tries to do everything in one shot and that's where it fails."
"There could be more customization options."
"Qlik's ETL and data transformation could be better."
"I believe that visual data flow management and the transformation function should be improved."
"I'd like to have access to more developer training materials."
"When processing data from certain tables with a large volume of data, we encounter significant delays. For instance, when dealing with around one million records, it typically takes three to four hours. To address this, I aim to implement performance improvements across all tables, ensuring swift processing similar to those that are currently complete within seconds. The performance issue primarily arises when we analyze the inserts and updates from the source, subsequently dropping the table. While new insertions are handled promptly, updates are processed slowly, leading to performance issues. Despite consulting our Qlik vendors, they were unable to pinpoint the exact cause of this occurrence. Consequently, I am seeking ways to optimize performance within Qlik Compose, specifically concerning updates."
"It would be better if the first level of technical support were a bit more technically knowledgeable to solve the problem. I think they could also improve the injection of custom scripts. It is pretty difficult to add additional scripts. If the modeling doesn't give you what you want, and you want to change the script generated by the modeling, it is a bit more challenging than in most other products. It is very good with standard form type systems, but if you get a more complicated data paradigm, it tends to struggle with transforming that into a model."
"It could enhance its capabilities in the realm of self-service options as currently, it is more suited for individuals with technical proficiency who can create pages using it."
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 Compose is ranked 18th in Data Integration with 12 reviews. AWS Database Migration Service is rated 7.8, while Qlik Compose is rated 7.6. 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 Compose writes "Easy matching and reconciliation of data". AWS Database Migration Service is most compared with AWS Glue, Oracle GoldenGate, Qlik Replicate, Fivetran and Confluent, whereas Qlik Compose is most compared with Qlik Replicate, Talend Open Studio, Oracle Data Integrator (ODI), Azure Data Factory and AWS Glue. See our AWS Database Migration Service vs. Qlik Compose 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.