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.8
Number of Reviews
71
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (9th), Search as a Service (1st), Vector Databases (3rd)
Qlik Compose
Average Rating
7.6
Reviews Sentiment
6.5
Number of Reviews
12
Ranking in other categories
Data Integration (33rd)
 

Featured Reviews

Anand_Kumar - PeerSpot reviewer
Captures data from all other sources and becomes a MOM aka monitoring of monitors
Scalability and ROI are the areas they have to improve. Their license terms are based on the number of cores. If you increase the number of cores, it becomes very difficult to manage at a large scale. For example, if I have a $3 million project, I won't sell it because if we're dealing with a 10 TB or 50 TB system, there are a lot of systems and applications to monitor, and I have to make an MOM (Mean of Max) for everything. This is because of the cost impact. Also, when you have horizontal scaling, it's like a multi-story building with only one elevator. You have to run around, and it's not efficient. Even the smallest task becomes difficult. That's the problem with horizontal scaling. They need to improve this because if they increase the cores and adjust the licensing accordingly, it would make more sense.
Sahil Taneja - PeerSpot reviewer
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 solution has good security features. I have been happy with the dashboards and interface."
"The full text search capabilities in Elastic Search have proven to be extremely valuable for our operations."
"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."
"I really like the visualization that you can do within it. That's really handy. Product-wise, it is a very good and stable product."
"The special text processing features in this solution are very important for me."
"I have found the sort capability of Elastic very useful for allowing us to find the information we need very quickly."
"X-Pack provides good features, like authorization and alerts."
"I appreciate that Elastic Enterprise Search is easy to use and that we have people on our team who are able to manage it effectively."
"The technical support is very good. I rate the technical support a ten out of ten."
"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."
"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."
"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."
"Qlik Compose is good enough. It is user-friendly and intuitive."
"It's a stable 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

"They could improve some of the platform's infrastructure management capabilities."
"Dashboards could be more flexible, and it would be nice to provide more drill-down capabilities."
"They should improve its documentation. Their official documentation is not very informative. They can also improve their technical support. They don't help you much with the customized stuff. They also need to add more visuals. Currently, they have line charts, bar charts, and things like that, and they can add more types of visuals. They should also improve the alerts. They are not very simple to use and are a bit complex. They could add more options to the alerting system."
"Ratio aggregation is not supported in this solution."
"Performance improvement could come from skipping background refresh on search idle shards (which is already being addressed in the upcoming seventh version)."
"The different applications need to be individually deployed."
"Elasticsearch should have simpler commands for window filtering."
"Its licensing needs to be improved. They don't offer a perpetual license. They want to know how many nodes you will be using, and they ask for an annual subscription. Otherwise, they don't give you permission to use it. Our customers are generally military or police departments or customers without connection to the internet. Therefore, this model is not suitable for us. This subscription-based model is not the best for OEM vendors. Another annoying thing about Elasticsearch is its roadmap. We are developing something, and then they say, "Okay. We have removed that feature in this release," and when we are adapting to that release, they say, "Okay. We have removed that one as well." We don't know what they will remove in the next version. They are not looking for backward compatibility from the customers' perspective. They just remove a feature and say, "Okay. We've removed this one." In terms of new features, it should have an ODBC driver so that you can search and integrate this product with existing BI tools and reporting tools. Currently, you need to go for third parties, such as CData, in order to achieve this. ODBC driver is the most important feature required. Its Community Edition does not have security features. For example, you cannot authenticate with a username and password. It should have security features. They might have put it in the latest release."
"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."
"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."
"There is some scope for improvement around the documentation, and a better UI would definitely help."
"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."
"There should be proper documentation available for the implementation process."
"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."
 

Pricing and Cost Advice

"We are using the open-sourced version."
"The tool is not expensive. Its licensing costs are yearly."
"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
"This product is open-source and can be used free of charge."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"The solution is less expensive than Stackdriver and Grafana."
"It can move from $10,000 US Dollars per year to any price based on how powerful you need the searches to be and the capacity in terms of storage and process."
"An X-Pack license is more affordable than Splunk."
"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.
861,803 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Financial Services Firm
14%
Manufacturing Company
9%
Government
9%
Financial Services Firm
16%
Manufacturing Company
9%
Government
8%
Computer Software Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
We used the open-source version of Elasticsearch, which was free.
What needs improvement with ELK Elasticsearch?
It would be useful if a feature for renaming indices could be added without affecting the performance of other features. However, overall, the consistency and stability of Elasticsearch are already...
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...
What do you like most about Qlik Compose?
The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities.
What is your experience regarding pricing and costs for Qlik Compose?
While they outperform Tableau, there's room for improvement in Qlik's pricing structures, especially for corporate clients like us.
 

Comparisons

 

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: July 2025.
861,803 professionals have used our research since 2012.