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

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

Redis
Ranking in NoSQL Databases
3rd
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
27
Ranking in other categories
Managed NoSQL Databases (5th), In-Memory Data Store Services (1st), Vector Databases (3rd), AI Software Development (9th)
ScyllaDB
Ranking in NoSQL Databases
7th
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 August 2026, in the NoSQL Databases category, the mindshare of Redis is 8.3%, down from 9.1% compared to the previous year. The mindshare of ScyllaDB is 5.9%, down from 10.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Redis8.3%
ScyllaDB5.9%
Other85.8%
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

"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"Overall, Redis helps us design more efficient applications by improving performance while allowing our backend services to scale more effectively."
"Redis is a simple, powerful, and fast solution."
"Redis is good for distributed caching management."
"The solution is fast, provides good performance, and is not too expensive."
"The performance of Redis is very fast."
"Redis acts as an in-memory search tool that improves the speed of operations, allowing for quicker data retrieval and enhancing the performance of applications."
"The in-memory data makes it fast."
"Scalability in performance is good."
"The performance and scalability are good, and we hardly see any major issues with ScyllaDB."
"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."
"ScyllaDB is fast and reliable. It has good performance."
"The documentation is good. It integrates easily with our existing data infrastructure."
"It is lightweight, and it requires less infrastructure."
"The product's most valuable features are efficiency and reliability."
"The database is easy to use, fast, and accessible for applications because the API is straightforward."
 

Cons

"There is a lack of documentation on the scalability of the solution."
"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."
"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."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"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 first challenge is memory limitations, as Redis is primarily in-memory, making memory usage a key constraint."
"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."
"The product needs to add more features and improve the response time of the support team."
"We've had occasional performance challenges that required resource adjustments or optimizations in our interaction with the platform."
"Support and the availability of support need improvement. I would give them a six out of ten."
"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."
"From a sales pitch standpoint, it needs to deliver on promises of better ROI and compaction."
"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."
"The documentation of Scylla is an area with shortcomings and needs to be improved."
 

Pricing and Cost Advice

"The tool is open-source. There are no additional costs."
"Redis is an open-source solution. There are not any hidden fees."
"Redis is an open-source product."
"Redis is not an overpriced solution."
"We saw an ROI. It made the processing of our transactions faster."
"It's free."
"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."
"I believe that there is a yearly licensing cost and that it's expensive."
"It's a bit expensive."
"It is an expensive tool compared to its competitor."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
907,787 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Computer Software Company
10%
Comms Service Provider
6%
University
6%
Outsourcing Company
14%
Comms Service Provider
9%
Financial Services Firm
8%
Transportation Company
7%
 

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?
I have faced a few challenges and limitations with Redis. Although it is extremely powerful, there are challenges and areas for improvement depending on the use case. The first challenge is memory ...
What is your primary use case for Redis?
The main use case for Redis is caching. Caching is the primary purpose of using Redis for my organization, as I use it to cache frequently accessed data to improve application performance and reduc...
What advice do you have for others considering Redis?
If somebody is looking to use Redis, it is much easier and more scalable for making most database queries faster, especially for repeated pages while fetching data. It helps tremendously in handlin...
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: June 2026.
907,787 professionals have used our research since 2012.