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

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
12th
Average Rating
8.0
Reviews Sentiment
6.0
Number of Reviews
25
Ranking in other categories
NoSQL Databases (6th)
Elastic Search
Ranking in Vector Databases
5th
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)
 

Mindshare comparison

As of June 2026, in the Vector Databases category, the mindshare of Cassandra is 3.5%, up from 1.9% compared to the previous year. The mindshare of Elastic Search is 4.7%, down from 4.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases Mindshare Distribution
ProductMindshare (%)
Elastic Search4.7%
Cassandra3.5%
Other91.8%
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.
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.

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 Cassandra are the NoSQL database, high performance, and zero-copy streaming."
"It's used as our cloud based backend store as a temporary cache and for storing data that streams through our data pipe."
"We have experienced zero downtime using Cassandra, it is highly stable."
"Can achieve continuous data without a single downtime because of node to node ring architecture."
"Cassandra is good, it's better than CouchDB, and we are using it in parallel with CouchDB, as Cassandra looks better and is more user-friendly."
"I am getting much better performance than relational databases."
"The most valuable features of this solution are its speed and distributed nature."
"If you need availability and consistency, you can go with Cassandra."
"The initial setup is very easy for small environments."
"The dashboard is a valuable feature - it's awesome and very customizable."
"It is highly valuable because of its simplicity in maintenance, where most tasks are handled for you, and it offers a plethora of built-in features."
"The solution offers good stability."
"Aggregation is faster than querying directly from a database, like Postgres or Vertica, and it's much faster if I want to do aggregation, which allows me to store logs and find anomalies effectively."
"I am impressed with the product's Logstash. The tool is fast and customizable. You can build beautiful dashboards with it. It is useful and reliable."
"From a technical point of view, there are no significant issues recalled as Elastic Search has been absolutely awesome for this use case and covers 100% of the needs."
"The most valuable features are the ease and speed of the setup."
 

Cons

"Cassandra is very complex to manage. Sometimes, I need to involve a senior DevOps engineer if we encounter a problem."
"Row-level locking is not available; might be very helpful in update use cases."
"The solution doesn't have joins between tables so you need other tools for that."
"Depending upon our schema, we can't make ORDER BY or GROUP BY clauses in the product."
"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."
"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."
"It can be difficult to analyze what's going on inside of the database relative to other databases. It can also be difficult to troubleshoot sometimes."
"One of the issues with the solution is that you cannot drop write like you're able to in MongoDB and MySQL, where you can join tables."
"They should improve its documentation. Their official documentation is not very informative."
"Something that could be improved is better integrations with Cortex and QRadar, for example."
"I found an issue with Elasticsearch in terms of aggregation. There is a maximum of 10,000 entries, so the limitation means that if I wanted to analyze certain IP addresses more than 10,000 times, I wouldn't be able to dump or print that information."
"Could have more open source tools and testing."
"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."
"I want the solution to improve the graph feature because it is a little bit poor."
"Pagination in Elastic Search is very slow."
"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."
 

Pricing and Cost Advice

"Cassandra is a free open source solution, but there is a commercial version available called DataStax Enterprise."
"I use the tool's open-source version."
"We are using the open-source version of Cassandra, the solution is free."
"There are licensing fees that must be paid, but I'm not sure if they are paid monthly or yearly."
"We pay for a license."
"I don't have the specific numbers on pricing, but it was fairly priced."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"To access all the features available you require both the open source license and the production license."
"There is a free version, and there is also a hosted version for which you have to pay. We're currently using the free version. If things go well, we might go for the paid version."
"The tool is not expensive. Its licensing costs are yearly."
"The price could be better."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"we are using a licensed version of the product."
"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."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
902,270 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
8%
Comms Service Provider
7%
Computer Software Company
6%
Financial Services Firm
12%
Manufacturing Company
9%
Computer Software Company
8%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise2
Large Enterprise14
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise49
 

Questions from the Community

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 is your primary use case for Cassandra?
My use case for Cassandra is for a document and other unstructured data management system as well as structured data for ultra-poor member community edition, community members' PII information, so ...
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.
 

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: April 2026.
902,270 professionals have used our research since 2012.