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

Elastic Search 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

Elastic Search
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
88
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (6th), Search as a Service (1st), Vector Databases (2nd)
Qlik Compose
Average Rating
7.6
Reviews Sentiment
6.5
Number of Reviews
12
Ranking in other categories
Data Integration (45th)
 

Featured Reviews

Vaibhav Shukla - PeerSpot reviewer
Senior Software Engineer at Agoda
Search performance has transformed large-scale intent discovery and hybrid query handling
While Elastic Search is a good product, I see areas for improvement, particularly regarding the misconception that any amount of data can simply be dumped into Elastic Search. When creating an index, careful consideration of data massaging is essential. Elastic Search stores mappings for various data types, which must remain below a certain threshold to maintain functionality. Users need to throttle the number of fields for searching to avoid overloading the system and ensure that the design of the document is efficient for the Elastic Search index. Additionally, I suggest utilizing ILM periodically throughout the year to manage data shuffling between clusters, preventing hotspots in the distribution of requests across nodes.
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 most valuable features of Elastic Enterprise Search are it's cloud-ready and we do a lot of infrastructure as code. By using ELK, we're able to deploy the solution as part of our ISC deployment."
"The most valuable feature for us is the analytics that we can configure and view using Kibana."
"The most valuable features are the detection and correlation features."
"The most valuable features are its user-friendly interface and seamless navigation."
"The tool's stability and performance are good."
"Elastic Search is the perfect tool for scalability."
"Elastic Search is very quick when handling a large volume of data."
"The full text search capabilities in Elastic Search have proven to be extremely valuable for our operations."
"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."
"The technical support is very good. I rate the technical support a ten out of ten."
"I have found it to be a very good, stable, and strong product."
"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."
"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."
"Qlik Compose is good enough. It is user-friendly and intuitive."
"It is a scalable solution."
 

Cons

"Pagination in Elastic Search is very slow."
"Something that could be improved is better integrations with Cortex and QRadar, for example."
"Machine learning on search needs improvement."
"Enterprise scaling of what have been essentially separate, free open source software (FOSS) products has been a challenge, but the folks at Elastic have published new add-ons (X-Pack and ECE) to help large companies grow ELK to required scales."
"The price could be better. Kibana has some limitations in terms of the tablet to view event logs. I also have a high volume of data. On the initialization part, if you chose Kibana, you'll have some limitations. Kibana was primarily proposed as a log data reviewer to build applications to the viewer log data using Kibana. Then it became a virtualization tool, but it still has limitations from a developer's point of view."
"I have not been using the solution for many years to know exactly the improvements needed. However, they could simplify how the YML files have to be structured properly."
"There is another solution I'm testing which has a 500 record limit when you do a search on Elastic Enterprise Search. That's the only area in which I'm not sure whether it's a limitation on our end in terms of knowledge or a technical limitation from Elastic Enterprise Search. There is another solution we are looking at that rides on Elastic Enterprise Search. And the limit is for any sort of records that you're doing or data analysis you're trying to do, you can only extract 500 records at a time. I know the open-source nature has a lot of limitations, Otherwise, Elastic Enterprise Search is a fantastic solution and I'd recommend it to anyone."
"Performance improvement could come from skipping background refresh on search idle shards (which is already being addressed in the upcoming seventh version)."
"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."
"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."
"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."
"I'd like to have access to more developer training materials."
"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."
"There could be more customization options."
"Qlik's ETL and data transformation could be better."
 

Pricing and Cost Advice

"The premium license is expensive."
"The solution is not expensive because users have the option of choosing the managed or the subscription model."
"We are using the Community Edition because Elasticsearch's licensing model is not flexible or suitable for us. They ask for an annual subscription. We also got the development consultancy from Elasticsearch for 60 days or something like that, but they were just trying to do the same trick. That's why we didn't purchase it. We are just using the Community Edition."
"This product is open-source and can be used free of charge."
"The tool is an open-source product."
"The pricing structure depends on the scalability steps."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"​The pricing and license model are clear: node-based model."
"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."
"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.
881,114 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Computer Software Company
12%
Manufacturing Company
10%
Government
6%
Financial Services Firm
15%
Government
12%
Manufacturing Company
9%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business37
Midsize Enterprise10
Large Enterprise43
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise6
 

Questions from the Community

What do you like most about ELK Elasticsearch?
Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time anal...
What is your experience regarding pricing and costs for ELK Elasticsearch?
Elastic Search's pricing totally depends on the server. Managed services from AWS are used, and we have worked on a self-managed Elastic Search cluster. On the AWS side, it is very expensive becaus...
What needs improvement with ELK Elasticsearch?
To be honest, there is only one downside of Elastic Search that makes sense because we use a basic license, which is a free license. We do not have some features available because of the free licen...
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

Elastic Enterprise Search, Swiftype, Elastic Cloud
Compose, Attunity Compose
 

Overview

 

Sample Customers

T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
Poly-Wood
Find out what your peers are saying about Elastic Search vs. Qlik Compose and other solutions. Updated: December 2025.
881,114 professionals have used our research since 2012.