AWS AppSync vs Qlik Compose comparison

"AWS has made it easy for developers like me to create and manage GraphQL APIs."

"Support for multiple data sources and formats is a fantastic feature."

"AWS has made it easy for developers like me to create and manage GraphQL APIs."

"It can scale."

"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's a stable solution."

"Qlik Compose is good enough. It is user-friendly and intuitive."

"The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities."

"I have found it to be a very good, stable, and strong product."

"The technical support is very good. I rate the technical support a ten out of ten."

"In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial."

"Moving to other clouds is impossible without significantly rearchitecting your applications."

"In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial."

"There should be proper documentation available for the implementation process."

"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."

"I believe that visual data flow management and the transformation function should be improved."

"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."

"Qlik's ETL and data transformation could be better."

"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."

"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."

"Licensing fees are paid on a monthly basis, and it is a pay-as-you-go model."

"The price of the solution is expensive."

"While they outperform Tableau, there's room for improvement in Qlik's pricing structures, especially for corporate clients like us."

"On a scale of one to ten, where one is cheap, and ten is very expensive, I rate the solution a six."