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

Redis vs ScyllaDB 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

Redis
Ranking in NoSQL Databases
3rd
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), Vector Databases (4th), AI Software Development (9th)
ScyllaDB
Ranking in NoSQL Databases
8th
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
12
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of September 2026, in the NoSQL Databases category, the mindshare of Redis is 8.0%, down from 8.8% compared to the previous year. The mindshare of ScyllaDB is 5.7%, down from 9.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Redis8.0%
ScyllaDB5.7%
Other86.3%
NoSQL Databases
 

Featured Reviews

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.
Manikandan Gunasekaran - PeerSpot reviewer
Director of Engineering at Ola
Reliable data management with great reliability and performance
From a sales pitch standpoint, it needs to deliver on promises of better ROI and compaction. Additionally, ticketing and support systems could be improved due to the time it takes to get answers. There's also an issue with compatibility when attempting to switch back from the enterprise to the community version.

Quotes from Members

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

Pros

"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 online interface is very fast and easy to use."
"The performance of Redis is very fast."
"It is particularly efficient for cloud-based storage and operations."
"The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast."
"The solution is fast, provides good performance, and is not too expensive."
"The in-memory data makes it fast."
"I use Redis mostly to cache repeated data that is required."
"The best features of ScyllaDB are how it synchronizes data and its failover system. There's a unique formula to decide the number of nodes you need and the minimum required, which I find helpful. It also offers encryption and supports APIs, making it great for distributed systems and scaling databases across different regions. While it's easy to use, having prior experience helps configure it properly. There are many configurations; if you don't understand them, you might mess up the design. So, understanding your system's needs, like whether it requires more read or write operations, is crucial for setting up the correct configuration."
"The performance aspects of Scylla are good, as always... A good point about Scylla is that it can be used extensively."
"The performance and scalability are good, and we hardly see any major issues with ScyllaDB."
"ScyllaDB allows fine-tuning of the table structure. Speed is probably the most critical factor because we perform a lot of heavy data ingestion. One of its core features is its ability to handle high volumes and maintain speed when accessing data. Additionally, high availability and partitioning are built-in features of ScyllaDB."
"I like how fast it is to query data from the ScyllaDB node!"
"The product's most valuable features are efficiency and reliability."
"The documentation is good. It integrates easily with our existing data infrastructure."
"Scalability in performance is good."
 

Cons

"Redis presents a single point of failure and lacks fault tolerance."
"The initial setup of Redis was difficult, with a rating of two or three out of ten."
"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."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"It's actually quite expensive."
"Redis should have an option to operate without Docker on a local PC."
"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."
"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."
"The product needs to add more features and improve the response time of the support team."
"Data export, along with how we can purchase the data periodically, needs to be improved so that the storage is within control. Then, we could optimize it even better."
"It seems we have better options available. So probably don't go for ScyllaDB. The reason is, first, it's very high. It's not as straightforward as, like, Postgres or ClickHouse to set up. It requires a complex setup."
"If you don't have the best computing resources, then it's not easy to set up. In such cases, we have to run ScyllaDB in developer mode."
"We faced several challenges while integrating ScyllaDB into our AWS environment. One common issue was that a security port wasn’t opened on one node, preventingdata synchronization across clusters. We noticed the data wasn’t syncing correctly when we saw different record counts in other regions. After investigating, we found that the port was closed in one AWS region. Once we opened the port, the data synchronization across all nodes resumed as expected."
"The documentation is not well established for new developers."
"The documentation of Scylla is an area with shortcomings and needs to be improved."
"ScyllaDB needs to improve its handling of transactions."
 

Pricing and Cost Advice

"We saw an ROI. It made the processing of our transactions faster."
"Redis is an open-source product."
"Redis is not an overpriced solution."
"The tool is open-source. There are no additional costs."
"Redis is an open-source solution. There are not any hidden fees."
"It is an expensive tool compared to its competitor."
"It's a bit expensive."
"The paid version of ScyllaDB is not that expensive. The main advantage of the paid version is direct support from the ScyllaDB team, which can resolve issues faster—typically within a day, compared to two to three days with the free version. The paid version also offers better guidance and support, while the free version has good documentation and is more high-level. I’d rate their support team nine out of ten because of the quick responses from their community."
"It's free."
"I believe that there is a yearly licensing cost and that it's expensive."
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
22%
Computer Software Company
9%
Comms Service Provider
7%
University
5%
Outsourcing Company
15%
Comms Service Provider
9%
Financial Services Firm
8%
Transportation Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise6
Large Enterprise10
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise8
 

Questions from the Community

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...
What is your experience regarding pricing and costs for Scylla?
From what I’ve seen (and experienced), ScyllaDB pricing is very dependent on how you deploy it, and that’s where most of the confusion comes from.
What needs improvement with Scylla?
From a sales pitch standpoint, it needs to deliver on promises of better ROI and compaction. Additionally, ticketing and support systems could be improved due to the time it takes to get answers. T...
What is your primary use case for Scylla?
We dump a lot of our data, such as every entry created with respect to when a user rides a scooter, every record gets updated to ScyllaDB. It is used as a single source of truth and it manages mass...
 

Comparisons

 

Also Known As

Redis Enterprise
No data available
 

Overview

 

Sample Customers

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
IBM, Investing.com, mParticle, Comcast, GE, Fanatics, Ola, CERN, adgear, Samsung
Find out what your peers are saying about Redis vs. ScyllaDB and other solutions. Updated: September 2026.
913,806 professionals have used our research since 2012.