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

Cassandra vs Redis comparison

 

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
6th
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
2nd
Average Rating
8.8
Reviews Sentiment
5.9
Number of Reviews
26
Ranking in other categories
Managed NoSQL Databases (6th), In-Memory Data Store Services (1st), AI Software Development (12th)
 

Mindshare comparison

As of June 2026, in the NoSQL Databases category, the mindshare of Cassandra is 8.3%, down from 10.6% compared to the previous year. The mindshare of Redis is 8.5%, up from 7.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Redis8.5%
Cassandra8.3%
Other83.2%
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.
Varuns Ug - PeerSpot reviewer
Senior Software Developer at NIT
Caching has accelerated complex workflows and delivers low latency for high-traffic microservices
A few features of Redis that I use on a day-to-day basis and feel are among the best are extremely low latency and high throughput. Since Redis is in-memory, it makes it ideal for cases such as caching and rate limiting where response time is critical. TTL expiry support is very useful in Redis as it allows me to automatically evict stale data without manual cleanup, which is something I use heavily in my caching strategy. Another point I can mention is that the rich data structures such as strings, hashes, and even sorted sets are very powerful. I have used strings for caching responses and counters, whereas I have used hashes for storing structured objects. One more feature I can tell you about is atomic operations. Redis guarantees atomicity for operations such as incrementing a counter, which is very useful for rate limiting and avoiding race conditions in distributed systems. Finally, I want to emphasize that Redis is easy to scale and integrate, whether through clustering or using a distributed cache across microservices. Redis has impacted my organization positively by providing default support that is very useful. For metrics, in one of my core systems, introducing Redis as a distributed cache helped me achieve around an 80% cache hit rate, which reduced repeated downstream services. Real API latency also improved from around two seconds to approximately 450 milliseconds for P99. It also helped reduce the load on dependent services and databases, which improved overall system reliability.

Quotes from Members

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

Pros

"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."
"It's used as our cloud based backend store as a temporary cache and for storing data that streams through our data pipe."
"The most valuable features of Cassandra are its scaling capabilities and its non-SQL nature capabilities."
"I am getting much better performance than relational databases."
"The technical evaluation is very good."
"Its retrieval is similar to an RDBMS, so our team finds it easy to adapt."
"Cassandra is a stable solution."
"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."
"The online interface is very fast and easy to use."
"Since I started using Redis, I feel that the product is saving me some performance tuning time."
"Redis is a powerful and reliable tool for improving application performance."
"Redis is good for distributed caching management."
"It is particularly efficient for cloud-based storage and operations."
"The in-memory data makes it fast."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"The best thing about Redis is its ability to handle large amounts of data without frequently hitting the database. You can store data in temporary memory, especially for high-volume data."
 

Cons

"The clustering needs to be better; it is getting there."
"We experience configuration issues when accommodating the volumes we require, which often necessitates consultation with the Cassandra development team."
"I want Cassandra to update its open-source version more quickly. It's already feature-rich, but I'd appreciate better integration with other NoSQL databases like MariaDB or MongoDB. If I ever need to work with customers or vendors using different NoSQL databases, having native integration in Cassandra would make managing and interacting with their databases much easier."
"The secondary index in Cassandra was a bit problematic and could be improved."
"Fine-tuning was a bit of a challenge."
"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 limited to a linear performance."
"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."
"There is a lack of documentation on the scalability of the solution."
"There are some points where I feel Redis can be improved."
"For the PubSub feature, we had to create our own tools to monitor the events."
"Redis presents a single point of failure and lacks fault tolerance."
"The solution's pricing for a local installation is very expensive."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"The only thing is the lack of a GUI application. There was a time when we needed to resolve an issue in production. If we had a GUI, it would have been easier."
"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."
 

Pricing and Cost Advice

"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."
"We are using the open-source version of Cassandra, the solution is free."
"I don't have the specific numbers on pricing, but it was fairly priced."
"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."
"Redis is an open-source product."
"Redis is not an overpriced solution."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is an open-source solution. There are not any hidden fees."
"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.
900,644 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
24%
Computer Software Company
10%
University
6%
Comms Service Provider
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 Business11
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?
Overall, Redis is a powerful and reliable tool, but there are a few areas for improvement. One limitation is that Redis is memory-based, so scaling can become expensive compared to disk-based syste...
What is your primary use case for Redis?
My main use case for Redis is caching frequently accessed data to improve performance and reduce database load. For example, I cache API responses and user-related data so that repeated requests ca...
What advice do you have for others considering Redis?
My main advice for those looking into using Redis is to focus on the use case; Redis excels where low latency is critical, such as caching, session management, or real-time features, rather than us...
 

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: May 2026.
900,644 professionals have used our research since 2012.