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

Cassandra vs InfluxDB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 7, 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 NoSQL Databases
5th
Average Rating
8.0
Reviews Sentiment
6.0
Number of Reviews
25
Ranking in other categories
Vector Databases (12th)
InfluxDB
Ranking in NoSQL Databases
6th
Average Rating
8.0
Reviews Sentiment
6.5
Number of Reviews
20
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), Network Monitoring Software (13th), IT Infrastructure Monitoring (14th)
 

Mindshare comparison

As of July 2026, in the NoSQL Databases category, the mindshare of Cassandra is 8.2%, down from 10.4% compared to the previous year. The mindshare of InfluxDB is 5.2%, down from 7.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Cassandra8.2%
InfluxDB5.2%
Other86.6%
NoSQL 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.
Mugeesh Husain - PeerSpot reviewer
Team Lead, Software at Energybox
Time series data has been managed efficiently for IoT sensors but reporting still needs improvement
How InfluxDB can be improved is relevant since for Energy Box, we face certain issues. We have customers worldwide, including the United States, United Kingdom, and Europe, but when we expanded to China two years ago, they indicated that they do not support the cloud version there. Our application is built on the cloud, which required us to create a separate application for Azure China, which was painful for us. The second issue involves frequent version changes. For example, we started with version one, transitioned to version two, and I heard they are considering InfluxDB version three, reverting to earlier practices. InfluxDB should improve without completely changing its approach. Now we have to redo our work for InfluxDB version three. Regarding needed improvements, the documentation is sufficient, but pricing presents a challenge. InfluxDB has standard pricing, which is acceptable for large companies. However, for startups in our position, they should provide special discounts so everyone can utilize it. The pricing should adapt as companies grow, which is a reasonable expectation.

Quotes from Members

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

Pros

"Since I haven't had years of experience with it, it's still new to me. One valuable feature is its distribution, so I can run it partly in the cloud and part on-prem. That's a feature I'd like to use but haven't yet because we're trying to move to Azure. I don't know if or when that will happen. Ideally, we'd have it distributed over the cloud and on-prem simultaneously, so if something happens to our on-prem, we can keep going in the cloud, like a pay-as-you-go model with Azure."
"The most valuable features are the counter features and the NoSQL schema, and it also has good scalability because you can scale Cassandra to any infinite level."
"Setup was very straightforward."
"The solution provided us with more than 100K PNRs a second and because the company was international there was a heavy data write, and at the same time a heavy data read."
"I am getting much better performance than relational databases."
"The most valuable feature for us is the technical evaluation, it's the best technology."
"I'd rate the solution ten out of ten."
"Ability to achieve write speeds 10k tps: Compared to existing, it is 300% percent higher."
"Because of reduced downtime, we benefit greatly from receiving alerts in advance."
"This product has been working well and it is serving our purpose, so I can recommend it to others."
"Prior to InfluxDB usage, real-time data was not visualized and monitored, and after the introduction of InfluxDB in the entire framework, the organization is benefiting a lot in terms of monitoring and understanding performance data in real-time."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"Overall, InfluxDB delivered excellent performance, stability, and simplicity for telemetry-driven use cases."
"InfluxDB positively impacts my organization because I have optimized my database storage, and by using powerful queries, I am able to find my data logs efficiently and also manage logging."
"Based on InfluxDB, we have great analytics produced by our SRE team, and with that, we have an alerting and monitoring system in place."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
 

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."
"The clustering needs to be better; it is getting there."
"The solution is limited to a linear performance."
"There were challenges with the query language and the development interface. The query language, in particular, could be improved for better optimization. These challenges were encountered while using the Java SDK."
"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."
"We experience configuration issues when accommodating the volumes we require, which often necessitates consultation with the Cassandra development team."
"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."
"The solution is not easy to use because it is a big database and you have to learn the interface. This is the case though in most of these solutions."
"I chose an 8 out of 10 because there is room for improvement, such as regarding backups and enhanced security through other types of authentication or encrypted data in TLS."
"However, I do wish the documentation and community resources around Flux were more extensive and beginner-friendly."
"InfluxDB can be improved in several ways. The Flux query language needs to be learned, but if there were something similar to SQL or previous options, it would be much easier for users without imposing a learning curve."
"I haven't seen a return on investment; unfortunately, I cannot share relevant metrics such as time saved, fewer employees needed, or money saved."
"InfluxDB cannot be used for high-cardinality data. It's also difficult and time-consuming to write queries, and there are some issues with bulk API."
"InfluxDB can be improved by addressing issues such as performance drops, queries being more difficult to understand, and its high memory usage."
"Sometimes, when we write too much data within a minute, the data count becomes excessive, reaching perhaps 100,000 or 500,000 data points, and InfluxDB gives a timeout exception, which we must handle in our application."
"In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version."
 

Pricing and Cost Advice

"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."
"I use the tool's open-source version."
"Cassandra is a free open source solution, but there is a commercial version available called DataStax Enterprise."
"The tool is an open-source product."
"InfluxDB is open-source, but there are additional costs for scaling."
"We are using the open-source version of InfluxDB."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
903,067 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
8%
Comms Service Provider
7%
Performing Arts
6%
Financial Services Firm
12%
Manufacturing Company
10%
Comms Service Provider
9%
Construction Company
9%
 

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 Business9
Midsize Enterprise5
Large Enterprise9
 

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 needs improvement with InfluxDB?
If the dashboarding facility can be improved in terms of the visualization parameters and the amount of support available from the community, as well as having smarter alerts to send those alerts t...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is to inject all my performance data and visualize it as a data source into Grafana. My data comes from JMeter from a plugin, which is inserting data to InfluxDB, and ...
What advice do you have for others considering InfluxDB?
It is good to start with InfluxDB to stabilize your data, visualize your data, and have the data stored on a time-series basis. I would recommend everyone to get into InfluxDB and start using it. T...
 

Comparisons

 

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
ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
Find out what your peers are saying about Cassandra vs. InfluxDB and other solutions. Updated: June 2026.
903,067 professionals have used our research since 2012.