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

Cassandra 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

Cassandra
Ranking in Vector Databases
14th
Average Rating
8.0
Reviews Sentiment
6.0
Number of Reviews
25
Ranking in other categories
NoSQL Databases (7th)
Elastic Search
Ranking in Vector Databases
2nd
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
90
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (6th), Search as a Service (1st)
 

Mindshare comparison

As of March 2026, in the Vector Databases category, the mindshare of Cassandra is 2.6%, up from 1.7% compared to the previous year. The mindshare of Elastic Search is 4.0%, down from 6.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases Mindshare Distribution
ProductMindshare (%)
Elastic Search4.0%
Cassandra2.6%
Other93.4%
Vector Databases
 

Featured Reviews

Monirul Islam Khan - PeerSpot reviewer
Head, Data Integration & Management at a non-profit with 10,001+ employees
Has maintained secure document storage and efficient data distribution with peer-to-peer architecture
The functions or features in Cassandra that I have found most valuable are that it is a distributed system similar to Mongo. It's good enough for comparison with another SQL database, so it's smooth and organized for distributed database system. The peer-to-peer architecture in Cassandra is helpful for network decentralization, and I have already introduced that feature. Cassandra features in peer-to-peer as well as another monitoring, so basically, it's good enough for our service. The tunable consistency level in Cassandra is good, and we are using that feature already. In terms of built-in caching and lightweight transactions in Cassandra, the transaction level is good, and it's optimized, so there are no more issues in that database. Based on my experience, Cassandra is good for document management system, as well as distributed database system, and the automatic recovery process is there. Additionally, the database monitoring system or auditing system is well-comparable with other database systems, so we are actually happy to be using this Cassandra database.
Anurag Pal - PeerSpot reviewer
Technical Lead at a consultancy with 10,001+ employees
Search and aggregations have transformed how I manage and visualize complex real estate data
Elastic Search consumes lots of memory. You have to provide the heap size a lot if you want the best out of it. The major problem is when a company wants to use Elastic Search but it is at a startup stage. At a startup stage, there is a lot of funds to consider. However, their use case is that they have to use a pretty significant amount of data. For that, it is very expensive. For example, if you take OLTP-based databases in the current scenario, such as ClickHouse or Iceberg, you can do it on 4GB RAM also. Elastic Search is for analytical records. You have to do the analytics on it. According to me, as far as I have seen, people will start moving from Elastic Search sooner or later. Why? Because it is expensive. Another thing is that there is an open source available for that, such as ClickHouse. Around 2014 and 2012, there was only one competitor at that time, which was Solr. But now, not only is Solr there, but you can take ClickHouse and you have Iceberg also. How are we going to compete with them? There is also a fork of Elastic Search that is OpenSearch. As far as I have seen in lots of articles I am reading, users are using it as the ELK stack for logs and analyzing logs. That is not the exact use case. It can do more than that if used correctly. But as it involves lots of cost, people are shifting from Elastic Search to other sources. When I am talking about pricing, it is not only the server pricing. It is the amount of memory it is using. The pricing is basically the heap Java, which is taking memory. That is the major problem happening here. If we have to run an MVP, a client comes to me and says, "Anurag, we need to do a proof of concept. Can we do it if I can pay a 4GB or 16GB expense?" How can I suggest to them that a minimum of 16GB is needed for Elastic Search so that your proof of concept will be proved? In that case, what I have to suggest from the beginning is to go with Cassandra or at the initial stage, go with PostgreSQL. The problem is the memory it is taking. That is the only thing.

Quotes from Members

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

Pros

"We can add almost one million columns to the solution."
"Cassandra has some features that are more useful for specific use cases where you have time series where you have huge amounts of writes. That should be quick, but not specifically the reads. We needed to have quicker reads and writes and this is why we are using Cassandra right now."
"Our primary use case for the solution is testing."
"I am satisfied with the performance."
"The most valuable features of Cassandra are its scaling capabilities and its non-SQL nature capabilities."
"The most valuable feature of Cassandra is its fast retrieval. Additionally, the solution can handle large amounts of data. It is the quickest application we use."
"I am getting much better performance than relational databases."
"A consistent solution."
"The most valuable features are the ease and speed of the setup."
"The security portion of Elasticsearch is particularly beneficial, allowing me to view and analyze security alerts."
"The machine learning features of Elastic Search are very interesting, including the possibility to include models such as ELSER and different multilingual models that let us fine-tune our searches and use them in our search projects."
"The most valuable feature of Elastic Enterprise Search is the opportunity to search behind and between different logs."
"Elastic is doing a fantastic job by doing the indexing, and with a couple of indexing configurations, we are able to achieve our goal even though we are maintaining a huge amount of data per day, around millions of transactions for each record."
"Data indexing of historical data is the most beneficial feature of the product."
"The most valuable feature for us is the analytics that we can configure and view using Kibana."
"The tool's stability and performance are good."
 

Cons

"The initial setup of Cassandra can be difficult in the configuration. There might be a need to have assistance. The implementation process can six months for connecting to certain databases."
"While Cassandra can handle NoSQL, I think there should be more flexibility for whole schema design when data is stored in wide columns. Additionally, I believe that eventual consistency should be enhanced."
"Cassandra could be more user-friendly like MongoDB."
"Cassandra can improve by adding more built-in tools. For example, if you want to do some maintenance activities in the cluster, we have to depend on third-party tools. Having these tools build-in would be e benefit."
"Fine-tuning was a bit of a challenge."
"We found some issues with the batch inserts when the data volume is large."
"We experience configuration issues when accommodating the volumes we require, which often necessitates consultation with the Cassandra development team."
"The solution doesn't have joins between tables so you need other tools for that."
"The GUI is the part of the program which has the most room for improvement."
"Elastic Search needs to improve authentication. It also needs to work on the Kibana visualization dashboard."
"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."
"The different applications need to be individually deployed."
"Kibana should be more friendly, especially when building dashboards."
"According to me, as far as I have seen, people will start moving from Elastic Search sooner or later. Why? Because it is expensive."
"Improving machine learning capabilities would be beneficial."
"Ratio aggregation is not supported in this solution."
 

Pricing and Cost Advice

"We pay for a license."
"I use the tool's open-source version."
"There are licensing fees that must be paid, but I'm not sure if they are paid monthly or yearly."
"I don't have the specific numbers on pricing, but it was fairly priced."
"We are using the open-source version of Cassandra, the solution is free."
"Cassandra is a free open source solution, but there is a commercial version available called DataStax Enterprise."
"We are using the free open-sourced version of this solution."
"​The pricing and license model are clear: node-based model."
"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."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
"To access all the features available you require both the open source license and the production license."
"The cost varies based on factors like usage volume, network load, data storage size, and service utilization. If your usage isn't too extensive, the cost will be lower."
"We are using the free version and intend to upgrade."
"The premium license is expensive."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
884,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Computer Software Company
7%
Comms Service Provider
7%
Retailer
7%
Financial Services Firm
12%
Computer Software Company
11%
Manufacturing Company
9%
Retailer
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise1
Large Enterprise14
By reviewers
Company SizeCount
Small Business38
Midsize Enterprise10
Large Enterprise45
 

Questions from the Community

What do you like most about Cassandra?
The use of Cassandra in real-time data analytics has been pivotal for our e-commerce platform. As our platform operates 24/7, providing services to sellers and customers alike, the need for real-ti...
What is your experience regarding pricing and costs for Cassandra?
The pricing for Cassandra is a little bit high, so it would be better for our community services if they consider community pricing for any non-profit organization like an NGO or other things. It w...
What needs improvement with Cassandra?
Regarding areas of improvement for Cassandra, currently, we are not facing significant issues. Some issues arise from our vendors like Apache slowness and distribution or load balancing from HAProx...
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?
On the subject of pricing, Elastic Search is very cost-efficient. You can host it on-premises, which would incur zero cost, or take it as a SaaS-based service, where the expenses remain minimal.
What needs improvement with ELK Elasticsearch?
From the UI point of view, we are using most probably Kibana, and I think they can do much better than that. That is something they can fine-tune a little bit, and then it will definitely be a good...
 

Comparisons

 

Also Known As

No data available
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Overview

 

Sample Customers

1. Apple 2. Netflix 3. Facebook 4. Instagram 5. Twitter 6. eBay 7. Spotify 8. Uber 9. Airbnb 10. Adobe 11. Cisco 12. IBM 13. Microsoft 14. Yahoo 15. Reddit 16. Pinterest 17. Salesforce 18. LinkedIn 19. Hulu 20. Airbnb 21. Walmart 22. Target 23. Sony 24. Intel 25. Cisco 26. HP 27. Oracle 28. SAP 29. GE 30. Siemens 31. Volkswagen 32. Toyota
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 Cassandra vs. Elastic Search and other solutions. Updated: February 2026.
884,873 professionals have used our research since 2012.