No more typing reviews! Try our Samantha, our new voice AI agent.

AWS Glue vs Qlik Compose comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

AWS Glue
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
50
Ranking in other categories
Cloud Data Integration (1st)
Qlik Compose
Average Rating
7.6
Reviews Sentiment
6.5
Number of Reviews
12
Ranking in other categories
Data Integration (50th)
 

Featured Reviews

SC
application security engineer at Hyperspace IT India
Efficient data integration reduces operational time and enhances metadata management
For the initial setup with AWS Glue, I find it easy to set up the data catalog and create Glue jobs using the visual editor or the visual code. Setting permission sets via IAM rules can be a bit tricky at the start, but we ensure Glue has access to AWS S3, Redshift, and other services. Once the role is configured, it runs smoothly. For advanced configurations, connecting to VPCs and setting up connections with JDBC sources takes more time compared to my cloud experience, but overall, for someone with cloud and ETL experience, the setup is manageable and well done.
Sahil Taneja - PeerSpot reviewer
Principal Consultant/Manager at Tenzing
Easy matching and reconciliation of data
The initial setup was easy for the data warehousing concept. But for a person who is new to ETL and warehousing concepts, it may take some time. If someone is familiar with these concepts, they could understand and learn the tool quickly. However, compared to other tools, the UI is complex. It would be helpful to have a better UI and documentation for new users. As of now, there is a challenge in learning the Compose tool for new users altogether. Qlik Compose was deployed on-premises. But the servers, like the SQL servers were maintained on the cloud—the managed instances.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"What I like best about AWS Glue is its real-time data backup feature. Last week, there was a production push, and what used to take almost ten days to send out around fifty-six thousand emails now takes only two hours."
"The two features I find most valuable in AWS Glue are its user interface and ease of use."
"The solution integrates well with other AWS products or services."
"The most valuable feature for me is the visual interface of AWS Glue."
"Glue is a NoSQL-based data ETL tool that has some advantages over IIS and ISAs."
"For ETL, I feel the performance is excellent."
"Transformations are valuable because you can modify or override complex data logic from an open source or Spark to solve issues."
"It is a stable and scalable solution."
"It's a stable solution."
"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."
"Qlik Compose is good enough. It is user-friendly and intuitive."
"It can scale."
"The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities."
"It is a scalable solution."
"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."
 

Cons

"The solution should offer features for streaming data in addition to batching data."
"I would like to see a more robust interface on the no-code side. This would be nice to be able to split cells."
"If there's a cluster-related configuration, we have to make worker notes, which is quite a headache when processing a large amount of data."
"The price of the solution could improve."
"It is not clear how the partition discovery would have been affected by more data coming in."
"In the building and deployment aspects, there is room for improvement. The current process is a bit complicated and could benefit from being more user-friendly and simpler, which would help speed up the deployment process."
"The solution could be cheaper. The price of the solution is an area that needs improvement."
"I would like to see stable libraries at the moment they are not there."
"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."
"I believe that visual data flow management and the transformation function should be improved."
"The solution has room for improvement in the ETL. They have an ETL, but when it comes to the monitoring portion, Qlik Compose doesn't provide a feature for monitoring."
"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."
"The solution has room for improvement in the ETL. They have an ETL, but when it comes to the monitoring portion, Qlik Compose doesn't provide a feature for monitoring."
"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 don't think Qlik can be used in a high-volume scenario. It didn't work for us."
"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."
 

Pricing and Cost Advice

"The solution's pricing is based on DPUs so it is a good idea to optimize use or it can get expensive."
"AWS Glue uses a pay-as-you-go approach which is helpful. The price of the overall solution is low and is a great advantage."
"AWS Glue is quite costly, especially for small organizations."
"I rate the tool's pricing a four out of ten."
"AWS Glue follows a pay-as-you-go model, wherein the cost of the data you use will be counted as a monthly bill."
"The pricing is a bit higher than other solutions like Athena and EC2. If the pricing becomes more scaled or flexible, it will be good because you have to pay 44 cents just for one DPU for an hour. If you increase DPUs to 5 or 10, the pricing gets multiplied. There are also some time limits like 0 to 10 minutes or 10 to 20 minutes. If the pricing is according to the minutes, it would be better because you have to limit your job to 10 minutes or 20 minutes."
"Technical support is a paid service, and which subscription you have is dependent on that. You must pay one of them, and it ranges from $15,000 to $25,000 per year."
"I rate the tool an eight on a scale of one to ten, where one is expensive, and ten is expensive."
"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."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
892,678 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
9%
Manufacturing Company
8%
Comms Service Provider
6%
Financial Services Firm
12%
Government
11%
Manufacturing Company
9%
Construction Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise6
Large Enterprise32
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise6
 

Questions from the Community

How do you select the right cloud ETL tool?
AWS Glue and Azure Data factory for ELT best performance cloud services.
How does Talend Open Studio compare with AWS Glue?
We reviewed AWS Glue before choosing Talend Open Studio. AWS Glue is the managed ETL (extract, transform, and load) from Amazon Web Services. AWS Glue enables AWS users to create and manage jobs in...
What are the most common use cases for AWS Glue?
AWS Glue's main use case is for allowing users to discover, prepare, move, and integrate data from multiple sources. The product lets you use this data for analytics, application development, or ma...
Which ETL tool would you recommend to populate data from OLTP to OLAP?
There are two products I know about * TimeXtender : Microsoft based, Transformation logic is quiet good and can easily be extended with T-SQL , Has a semantic layer that generates metat data for cu...
 

Also Known As

No data available
Compose, Attunity Compose
 

Overview

 

Sample Customers

bp, Cerner, Expedia, Finra, HESS, intuit, Kellog's, Philips, TIME, workday
Poly-Wood
Find out what your peers are saying about AWS Glue vs. Qlik Compose and other solutions. Updated: April 2026.
892,678 professionals have used our research since 2012.