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

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
99
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (6th)
Qlik Compose
Average Rating
7.6
Reviews Sentiment
6.5
Number of Reviews
12
Ranking in other categories
Data Integration (51st)
 

Featured Reviews

reviewer2817942 - PeerSpot reviewer
Senior Software Engineer at a consultancy with 11-50 employees
Logging and vector search have transformed observability and empowered reliable ai agents
Elastic Search is not specifically being used for certain purposes. I deploy Elastic Search database on the cloud and use cloud services so that nobody can attack. However, I do not use Elastic Search to resolve attack issues. The basic main purpose of Elastic Search, as of now, I feel it can do more in the AI area. Sometime I saw that when I am developing RAG and have to generate the embeddings, which I call metadata, sometimes it tries to fail. That durability or issue handling should be improved, but apart from that, I did not find anything as of now. As per my use case, whatever I am using seems pretty good. Apart from that, some definitely improvement will be there. One improvement is that it should be faster. Whenever I am searching any logs, it takes much time. For example, if I open my log in Notepad or a similar tool, I can search the text within a second. With Elastic Search, it takes a little bit of time, ten to fifteen seconds. That can be improved. Sometimes, engineers take time to assign when I create a ticket.
SA
Director - Metrics & Analytics at a computer software company with 1,001-5,000 employees
Efficient data warehouse automation with robust features, but may require enhancements in user-friendly self-service options and pricing flexibility for broader corporate appeal
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. When it comes to end users who may lack technical expertise, they are limited to toggling between existing developments. To empower end users to make critical changes without relying heavily on technical expertise, it would be beneficial to introduce more user-friendly features for development and modification. If it could incorporate correlation analysis capabilities into its platform, especially in a user-friendly manner, it would greatly enhance the tool's overall utility and make it an even more outstanding solution. There is a room for improvement regarding stability.

Quotes from Members

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

Pros

"My favorite feature is the ease of use, particularly in how you integrate the agent; I've been using it since version 7, and we're on version 9 now, and I've seen the progress from using Beats to using the agent, making it so simple today to enroll a server with the Elastic Agent."
"ELK being an open source certainly provided a platform for our organization to get involved."
"ELK Elasticsearch is 100% scalable as scalability is built into the design"
"Elastic Search's main advantages are the visuals that represent and visualize all entities and system components in a simplified diagram, which provides the ability to identify which component in the system has an issue."
"ELK Elasticsearch is a product that I recommend."
"The product is scalable with good performance."
"The AI-based attribute tagging is a valuable feature."
"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."
"It's a stable solution."
"I have found it to be a very good, stable, and strong product."
"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."
"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."
"It can scale."
"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."
 

Cons

"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 think the pricing of Elastic Search is really, really expensive."
"We see the need for some improvements with Elasticsearch. We would like the Elasticsearch package to include training lessons for our staff."
"The one area that can use improvement is the automapping of fields."
"The deployment was a struggle as I faced challenges with bash commands and understanding how to run things on my system."
"Elastic needs to work on their Machine Learning offering because currently they have been trying to make it a black box which doesn't work for a serious user (a Data Scientist) as it doesn't give any control over the underlying algorithm."
"There are a few things that did not work for us. When doing a search in a bigger setup, with a huge amount of data where there are several things coming in, it has to be on top of the index that we search."
"The pricing of this product needs to be more clear because I cannot understand it when I review the website."
"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."
"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'd like to have access to more developer training materials."
"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."
"Qlik's ETL and data transformation could be better."
"There should be proper documentation available for the implementation process."
"I don't think Qlik can be used in a high-volume scenario. It didn't work for us."
 

Pricing and Cost Advice

"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"This product is open-source and can be used free of charge."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
"The solution is less expensive than Stackdriver and Grafana."
"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."
"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."
"The price of Elastic Enterprise is very, very competitive."
"We use the free version for some logs, but not extensive use."
"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.
902,988 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise49
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise6
 

Questions from the Community

What is your experience regarding pricing and costs for ELK Elasticsearch?
Elastic Search is easy to use in Azure cloud. Mostly, my full company uses Azure cloud, so it is easy to use. Cost-wise, my company found Elastic Search is good. Cost matters. Based on cost and use...
What needs improvement with ELK Elasticsearch?
The initial configuration could be easier; at first, the learning curve is a little high, and over time, it becomes easier. For me, the initial configuration might be improved.
What is your primary use case for ELK Elasticsearch?
We use Elastic Search for a research application based on paper study, and the primary usage is for indexing the data and then functioning in a similar way to an e-commerce search bar.
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 Amazon Web Services (AWS), Informatica, Palantir and others in Cloud Data Integration. Updated: June 2026.
902,988 professionals have used our research since 2012.