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

Cassandra vs Redis comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 15, 2026

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
Ranking in Vector Databases
12th
Average Rating
8.0
Reviews Sentiment
6.0
Number of Reviews
25
Ranking in other categories
No ranking in other categories
Redis
Ranking in NoSQL Databases
3rd
Ranking in Vector Databases
4th
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
26
Ranking in other categories
Managed NoSQL Databases (5th), In-Memory Data Store Services (1st), AI Software Development (9th)
 

Mindshare comparison

As of September 2026, in the NoSQL Databases category, the mindshare of Cassandra is 8.3%, down from 8.7% compared to the previous year. The mindshare of Redis is 8.0%, down from 8.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Redis8.0%
Cassandra8.3%
Other83.7%
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.
RituRaj - PeerSpot reviewer
SDE 2 at Virtusa
Caching has improved response times and reduces database load for high-traffic applications
Redis is very reliable, but it could be improved in areas such as monitoring, debugging, and feasibility into memory use. Better built-in tools for observability would help teams manage it more effectively at scale. Managing memory efficiently and troubleshooting issues can sometimes require additional tooling, so these areas can also be improved.One practical challenge I experienced is managing memory efficiently. Since Redis is in-memory, we need to carefully configure eviction policies and monitor usage. Debugging cache-related issues such as stale data or cache invalidation can sometimes be tricky. Additionally, tuning memory usage and eviction policies needs to be planned very carefully.

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 feature for us is the technical evaluation, it's the best technology."
"A consistent solution."
"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."
"Some of the valued features of this solution are it has good performance and failover."
"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."
"Based on my experience, Cassandra is good for document management system, as well as distributed database system, and the automatic recovery process is there."
"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."
"Setup was very straightforward."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
"Overall, Redis helps us design more efficient applications by improving performance while allowing our backend services to scale more effectively."
"What I like best about Redis is its fast and easy use. It has interesting algorithms like HyperLogLog and provides useful features. It's also good for implementing scalable rate limiting."
"The ability to fetch and save data quickly is valuable."
"The product offers fast access to my database."
"Redis is good for distributed caching management."
"I use Redis mostly to cache repeated data that is required."
"I find Redis valuable primarily for its caching capabilities, particularly in handling cache requests effectively. Its simplicity in managing key-value pairs for caching is one of its strengths, making it a preferred choice over more complex databases like MongoDB for specific use cases. However, I haven't explored Redis extensively for managing complex data structures beyond caching, as MongoDB might be more suitable for such scenarios."
 

Cons

"We experience configuration issues when accommodating the volumes we require, which often necessitates consultation with the Cassandra development team."
"Some issues arise from our vendors like Apache slowness and distribution or load balancing from HAProxy, which should better handle consumption for high-level concurrency."
"If you have a requirement of aggregation and joints, Cassandra doesn't support a solution that can give the aggregation."
"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."
"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 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 disc space is lacking. You need to free it up as you are working."
"For the PubSub feature, we had to create our own tools to monitor the events."
"I would prefer it if there was more information available about Redis. That would make it easier for new beginners. Currently, there is a lack of resources."
"The disadvantage of Redis is that it's a little bit hard to have too many clusters or too many nodes and create the clusters."
"Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation."
"There are some features from MongoDB that I would like to see included in Redis to enhance its overall efficiency, such as the ability to perform remote behaviour. MongoDB is more efficient in handling updates than deletions and is quicker in processing updates, but it can be slower regarding deletions. This can sometimes pose a challenge, especially when dealing with large datasets or frequent data manipulations that involve deletions. In such cases, I often rewrite columns or update values instead of directly deleting data, as it can be more efficient."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"If we use a lot of data, it will eventually cost us a lot."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
 

Pricing and Cost Advice

"We pay for a license."
"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."
"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."
"Cassandra is a free open source solution, but there is a commercial version available called DataStax Enterprise."
"Redis is an open-source product."
"Redis is an open-source solution. There are not any hidden fees."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is not an overpriced solution."
"The tool is open-source. There are no additional costs."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Comms Service Provider
10%
Construction Company
7%
Outsourcing Company
7%
Financial Services Firm
22%
Computer Software Company
9%
Comms Service Provider
7%
University
5%
 

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 Business13
Midsize Enterprise6
Large Enterprise10
 

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 Redis?
Making management easier, especially for teams operating large Redis clusters, would be helpful. More advanced built-in observability, performance insights, and automated recommendations would help...
What is your primary use case for Redis?
Redis is used primarily as a caching layer to provide a high-performance caching solution that improves application response times and reduces load on backend services and databases. We use it main...
What advice do you have for others considering Redis?
There are a couple of things to consider when using Redis. It is a supporting layer, not a main database. Identifying specific use cases where Redis can provide the most value, such as caching, ses...
 

Comparisons

 

Also Known As

No data available
Redis Enterprise
 

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
1. Twitter 2. GitHub 3. StackOverflow 4. Pinterest 5. Snapchat 6. Craigslist 7. Digg 8. Weibo 9. Airbnb 10. Uber 11. Slack 12. Trello 13. Shopify 14. Coursera 15. Medium 16. Twitch 17. Foursquare 18. Meetup 19. Kickstarter 20. Docker 21. Heroku 22. Bitbucket 23. Groupon 24. Flipboard 25. SoundCloud 26. BuzzFeed 27. Disqus 28. The New York Times 29. Walmart 30. Nike 31. Sony 32. Philips
Find out what your peers are saying about Cassandra vs. Redis and other solutions. Updated: September 2026.
913,806 professionals have used our research since 2012.