AWS AppSync vs Qlik Compose comparison

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

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

"It's a stable solution."

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

"It is a scalable solution."

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

"There were many valuable features, such as extracting any data to put in the cloud. For example, Qlik was able to gather data from SAP and extract SAP data from the platforms."

"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."

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

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

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

"My issues with the solution's stability are owing to the fact that it has certain bugs causing issues in some functionalities that should be working."

"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 should be proper documentation available for the implementation process."

"There is some scope for improvement around the documentation, and a better UI would definitely help."

"There could be more customization options."

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

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

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

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

"The price of the solution is expensive."