Try our new research platform with insights from 80,000+ expert users

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

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

"The key role for Glue is that it hosts our metadata before rolling out our actual data. This is the major advantage of using this solution and our clients client have been very satisfied with it."
"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."
"It's fairly straightforward as a product; it's not very complicated."
"If I'm working with big data, common languages like Python work quite nicely, which is advantageous."
"The most valuable feature for me is the visual interface of AWS Glue."
"For ETL, I feel the performance is excellent."
"The most valuable feature of AWS Glue is that it provides a GUI format with a drag-and-drop feature."
"AWS Glue is a stable and easy-to-use solution."
"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."
"It is a scalable solution."
"I have found it to be a very good, stable, and strong product."
"It's a stable solution."
"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."
"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."
"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."
"It can scale."
 

Cons

"In terms of improvement, the performance of AWS Glue could be faster."
"The solution's visual ETL tool is of no use for actual implementation."
"I would like to see a more robust interface on the no-code side. This would be nice to be able to split cells."
"It would be better if it were more user-friendly. The interesting thing we found is that it was a little strange at the beginning. The way Glue works is not very straightforward. After trying different things, for example, we used just the console to create jobs. Then we realized that things were not working as expected. After researching and learning more, we realized that even though the console creates the script for the ETL processes, you need to modify or write your own script in Spark to do everything you want it to do. For example, we are pulling data from our source database and our application database, which is in Aurora. From there, we are doing the ETL to transform the data and write the results into Redshift. But what was surprising is that it's almost like whatever you want to do, you can do it with Glue because you have the option to put together your own script. Even though there are many functionalities and many connections, you have the opportunity to write your own queries to do whatever transformations you need to do. It's a little deceiving that some options are supposed to work in a certain way when you set them up in the console, but then they are not exactly working the right way or not as expected. It would be better if they provided more examples and more documentation on options."
"The process of entering environment variables in AWS Glue requires navigating to a different page, which could be streamlined."
"It fails to handle massive databases acquired from various sources."
"Improvements in the UI are needed, as it is challenging to understand some functionalities."
"Setting up pipelines is challenging, especially with version control and testing requirements."
"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."
"There should be proper documentation available for the implementation process."
"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."
"There could be more customization options."
"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."
"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."
 

Pricing and Cost Advice

"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."
"It is an expensive product. I rate its pricing a nine out of ten."
"I rate pricing an eight out of ten."
"The current cost is around forty to fifty thousand a month."
"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."
"It is not expensive. AWS Glue works on the serverless architecture. We get charged for the time the server is up. For our use case, we have to use it once in a day, and it is not expensive for us."
"AWS Glue follows a pay-as-you-go model, wherein the cost of the data you use will be counted as a monthly bill."
"I rate the tool an eight on a scale of one to ten, where one is expensive, and ten is expensive."
"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."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
883,011 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Computer Software Company
11%
Manufacturing Company
8%
Government
5%
Financial Services Firm
13%
Government
12%
Manufacturing Company
10%
Insurance Company
7%
 

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: February 2026.
883,011 professionals have used our research since 2012.