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 (48th)
 

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

"It is a very scalable solution."
"The solution is stable and reliable."
"Data catalog and triggers are the two best features for me. AWS Glue has its own data catalog, which makes it great and really easy to use. Triggers are also really good for scheduling the ETL process."
"You do not need many frameworks to run Glue."
"The price is very good; it's enticing people to move to the cloud."
"The most valuable feature for me is the visual interface of AWS Glue."
"AWS Glue is a highly stable solution."
"I like its integration and ability to handle all data-related tasks."
"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 is a scalable solution."
"Qlik Compose is good enough. It is user-friendly and intuitive."
"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."
"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."
"I like modeling and code generation. It has become a pretty handy tool because of its short ideation to delivery time. From the time you decide you are modeling a data warehouse, and once you finish the modeling, it generates all the code, generates all the tables. All you have to do is tick a few things, and you can produce a fully functional warehouse. I also like that they have added all the features I have asked for over four years."
"The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities."
"As long as you pick the solution that best fits with your requirements, you won't find that performance is a problem."
 

Cons

"There could be an enhanced way of managing pure metadata management or data cataloging."
"The product has only a few built-in transformations."
"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."
"It would be better if it were more user-friendly."
"On occasion, the solution's dashboard reports that a project failed due to runtime but it actually succeeded."
"Overall, I consider the technical support to be fine, although the response time could be faster in certain cases."
"The solution’s stability could be improved."
"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."
"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."
"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."
"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."
"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."
"Qlik's ETL and data transformation could be better."
"There should be proper documentation available for the implementation process."
"I believe that visual data flow management and the transformation function should be improved."
 

Pricing and Cost Advice

"Its price is good. We pay as we go or based on the usage, which is a good thing for us because it is simple to forecast for the tool. It is good in terms of the financial planning of the company, and it is a good way to estimate the cost. It is also simple for our clients. In my opinion, it is one of the best tools in the market for ETL processes because of the fact that you pay as you use, which separates it from other big tools such as PowerCenter, Pentaho Data Integration, and Talend."
"If you are using the solution for an enterprise business, it will be expensive."
"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 would rate the solution a six or seven on a scale of one to ten, with ten being very expensive. Specifically, I rate its pricing a six out of ten."
"It is an expensive product. I rate its pricing a nine out of ten."
"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."
"AWS Glue is a paid service that doesn't come under the free trial of AWS."
"The overall cost of AWS Glue could be better. It cost approximately $1,000 a month. There is paid support available from AWS Glue."
"On a scale of one to ten, where one is cheap, and ten is very expensive, I rate the solution a six."
"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."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
889,955 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
5%
Financial Services Firm
12%
Government
11%
Construction Company
11%
Manufacturing Company
9%
 

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.
889,955 professionals have used our research since 2012.