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

ClickHouse vs Elastic Search comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

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

ClickHouse
Ranking in Vector Databases
11th
Average Rating
8.8
Reviews Sentiment
7.8
Number of Reviews
11
Ranking in other categories
Open Source Databases (6th)
Elastic Search
Ranking in Vector Databases
3rd
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)
 

Mindshare comparison

As of June 2025, in the Vector Databases category, the mindshare of ClickHouse is 3.8%, up from 1.3% compared to the previous year. The mindshare of Elastic Search is 4.9%, down from 7.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases
 

Featured Reviews

Aswini Atibudhi - PeerSpot reviewer
Provides real-time data insights with high flexibility and responsive support
The basic challenge for ClickHouse is the documentation, which isn't ideal, but it's mature and stable with more columnar storage, compression, and parallel processing, making it the best for OLAP. In terms of improvements, it's not designed for very frequent small writes, making it less scalable in write-intensive workloads, and it's not flourishing in transactional use cases or when ingesting streaming data, such as batching or buffering, which is something ClickHouse will improve.
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.

Quotes from Members

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

Pros

"The main feature of ClickHouse is the optimizer because we had too many records to deduplicate, and the optimizer took this task by itself."
"ClickHouse is very easy to use; one of the good features is that it has joins, which were not present in Druid, and Druid was quite expensive, especially with our applications at Sam's Club utilizing ClickHouse very quickly."
"We faced a challenge with deploying ClickHouse onto Kubernetes. Recently, we've been using ClickHouse Cloud, and the main issue is the high cost of the cloud service. The pricing isn't very competitive, especially for startups. I would instead buy a server and self-host if I have enough disk space. Besides that, ClickHouse has done very well, with clear goals and effective execution."
"ClickHouse is much faster than traditional databases like MySQL and MongoDB. Its column-row searching strategy makes it very efficient. With ClickHouse, we can manage multiple databases, automatically insert data from other databases and delete data as needed. It supports real-time query performance, allowing simultaneous data insertion and retrieval. ClickHouse has improved significantly over the past two years, adding more functions and queries, as well as top functionality."
"The tool is column-based and infinitely scalable."
"It's easier to work with big data and calculations using the product."
"If you have a real-time basis, you should take a look at ClickHouse because it works on a vector database, and the querying is super fast compared to traditional databases."
"ClickHouse is a user-friendly solution that tries to be compatible with SQL standards."
"The initial setup is fairly simple."
"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."
"It is easy to scale with the cluster node model.​"
"The solution has great scalability."
"ELK Elasticsearch is 100% scalable as scalability is built into the design"
"Overall, considering key aspects like cost, learning curve, and data indexing architecture, Elasticsearch is a very good tool."
"The most valuable feature of Elastic Enterprise Search is the opportunity to search behind and between different logs."
"The solution offers good stability."
 

Cons

"The aggregation capability is a valuable feature. It's highly efficient, allowing us to review entire transaction histories and user activities in the market. We've tried MongoDB, Postgres, MariaDB, and BigQuery, but ClickHouse is the most cost-efficient solution for collecting data at high speeds with minimal cost. We even used ClickHouse Cloud for a month, and it proved to be a great setup, especially for startups looking to handle big data. For example, if there is a need for 2-4 terabytes of data and around 40 billion rows with reasonable computing speed and latency, ClickHouse is ideal. Regarding the real-time query performance of ClickHouse, when using an API server to query it, I achieved query results in less than twenty milliseconds in some of my experiments with one billion rows. However, it depends on the scenario since ClickHouse has limitations in handling mutations. Additionally, one of ClickHouse's strengths is its compression capability. Our experimental server has only four terabytes, and ClickHouse effectively compresses data, allowing us to store large amounts of data at high speed. This compression efficiency is a significant advantage of using ClickHouse."
"There aren't too many improvements I'd suggest for ClickHouse as it covers all my needs. There are just a few technical issues. For example, sometimes, when you want to get unique values and use certain tables, they don't work as expected. But it's not a major problem."
"We had a lot of troubles while deploying a whole cluster."
"In terms of improvements, it's not designed for very frequent small writes, making it less scalable in write-intensive workloads, and it's not flourishing in transactional use cases or when ingesting streaming data, such as batching or buffering, which is something ClickHouse will improve."
"I would like ClickHouse to work more on integration with third-party tools."
"If you join our team, it should be easy for you to use ClickHouse, especially if you are a developer. However, you need to read the documentation and understand the problems you are trying to solve."
"ClickHouse has its own concept of database triggers and doesn't support traditional database triggers."
"One issue is that you need persistent volumes. Otherwise, if one system goes down, you lose data in that cluster."
"I would rate the stability a seven out of ten. We faced a few issues."
"Something that could be improved is better integrations with Cortex and QRadar, for example."
"Elastic Search could benefit from a more user-friendly onboarding process for beginners."
"Technical support should be faster."
"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."
"Ratio aggregation is not supported in this solution."
"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."
"There are potential improvements based on our client feedback, like unifying the licensing cost structure."
 

Pricing and Cost Advice

"ClickHouse Cloud is not expensive compared to other databases, costing a few dollars per month while providing fast performance."
"If you have an in-house deployment on Kubernetes or something, it's going to be very cheap since you'll be managing everything."
"The tool is open-source."
"For pricing, if you use the self-hosted version, it would be free. Cloud services pricing would be an eight out of ten. I try to minimize costs but still have to monitor usage."
"ClickHouse has an open-source version, which is free to use and has almost all the features."
"We used the free, community version of ClickHouse."
"The tool is free."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"The premium license is expensive."
"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."
"It can be expensive."
"To access all the features available you require both the open source license and the production license."
"The price of Elasticsearch is fair. It is a more expensive solution, like QRadar. The price for Elasticsearch is not much more than other solutions we have."
"The solution is free."
"We are using the open-sourced version."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
857,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
25%
Financial Services Firm
15%
Educational Organization
11%
Manufacturing Company
8%
Computer Software Company
16%
Financial Services Firm
15%
Government
9%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What is your experience regarding pricing and costs for ClickHouse?
ClickHouse is open source without direct fees, unlike other databases that have hidden fees or restrict hosting to their platforms. The open-source nature of ClickHouse allows for complete flexibil...
What needs improvement with ClickHouse?
The basic challenge for ClickHouse is the documentation, which isn't ideal, but it's mature and stable with more columnar storage, compression, and parallel processing, making it the best for OLAP....
What is your primary use case for ClickHouse?
I have experience in ClickHouse ( /products/clickhouse-reviews ), and we also use Apache Druid ( /products/druid-reviews ), which has corporate support from Druid ( /products/druid-reviews ), along...
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...
 

Comparisons

 

Also Known As

No data available
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Overview

 

Sample Customers

Information Not Available
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.
Find out what your peers are saying about ClickHouse vs. Elastic Search and other solutions. Updated: April 2025.
857,028 professionals have used our research since 2012.