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

Cassandra vs InfluxDB vs Neo4j Graph Database 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:
 

Mindshare comparison

As of September 2025, in the NoSQL Databases category, the mindshare of Cassandra is 8.7%, down from 13.2% compared to the previous year. The mindshare of InfluxDB is 6.9%, down from 12.3% compared to the previous year. The mindshare of Neo4j Graph Database is 5.7%, up from 3.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Market Share Distribution
ProductMarket Share (%)
InfluxDB6.9%
Cassandra8.7%
Neo4j Graph Database5.7%
Other78.7%
NoSQL Databases
 

Featured Reviews

Himanshu Amodwala - PeerSpot reviewer
Well-equipped to handle a massive influx of data and billions of requests
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-time updates is paramount. For instance, when a customer leaves comments or feedback on an image, they anticipate an immediate reflection of these changes on the portal. Similarly, sellers altering product attributes or updating images expect instant visibility of these modifications. Handling large data volumes with Cassandra has been an excellent experience. Despite challenges related to the influx, these were not attributed to Cassandra itself but rather to middle-layer issues. Generally, it demonstrated scalability with workloads, thanks to its horizontal scaling capabilities. We could easily add new nodes to the system as needed, ensuring the platform coped well with increasing loads. The tool's most beneficial feature for scalability is its entire architecture. The absence of a single point of failure or a leader within the ecosystem contributes to its robust scalability. This key aspect influenced our decision to opt for the Cassandra ecosystem. In terms of performance, it demonstrated the ability to handle approximately 1.6 billion requests per day. This was achieved on AWS using EC2 instances, and it was during a period about four to five years ago.
DeepakR - PeerSpot reviewer
An open-source database that can be used to insert data
InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times.
RT
Delivers superior search and data aggregation capabilities
Neo4j helps with advanced search needs, providing good search results and aggregates compared to MongoDB. Aggregating with MongoDB can be difficult; however, with Neo4j, it's easier. Aggregating data, backing up, and creating new clusters are user-friendly from the back end. In DevOps web deployment, we noticed no database issues. We created Docker instances and set them up efficiently, managing databases up to 50 gigabytes.

Quotes from Members

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

Pros

"I'd rate the solution ten out of ten."
"I am getting much better performance than relational databases."
"Overall, I would rate Cassandra as nine because of its fast writes, which really suit our use cases mostly."
"I am satisfied with the performance."
"A consistent 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."
"Can achieve continuous data without a single downtime because of node to node ring architecture."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"InfluxDB reduced my time to show data without any interruption, also reducing the number of people needed to manage the project; it is very good to have InfluxDB in my project."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"While I would rate InfluxDB a ten on a scale of one to ten, users should be thoughtful about matching the engine to their specific needs."
"The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"The solution is very powerful."
"Creates the ability to visualize outputs."
"Enables people to understand what the business problem is and how the technology helps."
"The solution's best feature is how it differs from traditional SQL databases. It's hard to map people and find those near me in SQL, which requires long, complex queries. Neo4j Graph Database makes this easier with simpler queries. It also supports more data types, like JSON, which SQL doesn't."
"For now, the tool doesn't break down or stop, so it is quite stable."
"As a graph database, I am surprised at their performance and response time."
"It is good for search-based tasks, providing solid search results and aggregate results."
 

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."
"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."
"Depending upon our schema, we can't make ORDER BY or GROUP BY clauses in the product."
"The secondary index in Cassandra was a bit problematic and could be improved."
"Cassandra is very complex to manage. Sometimes, I need to involve a senior DevOps engineer if we encounter a problem."
"The solution is limited to a linear performance."
"Doesn't support a solution that can give aggregation."
"Batching bulk data can cause performance issues."
"The solution doesn't have much of a user interface."
"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."
"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"InfluxDB can improve by including new metrics on other technologies. They had some changes recently to pool data from endpoints but the functionality is not good enough in the industry."
"InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times."
"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."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"The solution's UI can be more user-friendly."
"The tool could improve by having more resources, especially for Golang, which we use. It lacks good basic libraries and doesn't have an ORM (Object-Relational Mapping) tool, which many NoSQL databases have. We thought about building an ORM for the Neo4j Graph Database but are too busy."
"The only problem is that the community is quite small."
"There are concerns about performance and whether the tool can necessarily scale to provide the solution."
"For me, when the tool was deployed on an on-premises model, it was a little bit difficult the first time."
"So far, we have not had any issues and are happy with the product in general."
 

Pricing and Cost Advice

"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."
"I don't have the specific numbers on pricing, but it was fairly priced."
"I use the tool's open-source version."
"We pay for a license."
"There are licensing fees that must be paid, but I'm not sure if they are paid monthly or yearly."
"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."
"InfluxDB recently increased its price. It is very expensive now."
"The solution is open source so that you can use it for free. They also offer an enterprise version with its billing. If your company is earning well, I suggest using the enterprise version. Otherwise, you can deploy it on your own cloud and pay based on usage."
"The tool is not expensive."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
868,304 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Computer Software Company
11%
Retailer
7%
Comms Service Provider
7%
Financial Services Firm
11%
Computer Software Company
10%
Manufacturing Company
9%
University
9%
Financial Services Firm
15%
Computer Software Company
11%
Energy/Utilities Company
8%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise1
Large Enterprise13
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise6
No data available
 

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 operat...
What needs improvement with Cassandra?
While Cassandra can handle NoSQL, I think there should be more flexibility for whole schema design when data is store...
What do you like most about InfluxDB?
InfluxDB is a database where you can insert data. However, it would be best if you had different components for alert...
What needs improvement with InfluxDB?
It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster. Replica...
What is your primary use case for InfluxDB?
InfluxDB is the main component in our large enterprise-scale streaming data application for maritime vessels. We coll...
What is your experience regarding pricing and costs for Neo4j?
The solution is open source so that you can use it for free. They also offer an enterprise version with its billing. ...
What needs improvement with Neo4j Graph Database?
The only problem is that the community is quite small.
What is your primary use case for Neo4j Graph Database?
We have used Neo4j in microservices. In one of the microservices, we used Neo4j since we have some requirements simil...
 

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
Walmart, Telenor, Wazoku, Adidas, Cerved, GameSys, eBay, Schleich, ICIJ, die Bayerisch, Megree, InfoJobs, LinkedIn
Find out what your peers are saying about MongoDB, Microsoft, ScyllaDB and others in NoSQL Databases. Updated: September 2025.
868,304 professionals have used our research since 2012.