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

Redis vs ScyllaDB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 7, 2025

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
7th
Average Rating
8.8
Reviews Sentiment
8.0
Number of Reviews
22
Ranking in other categories
In-Memory Data Store Services (1st), Vector Databases (4th)
ScyllaDB
Ranking in NoSQL Databases
2nd
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 April 2025, in the NoSQL Databases category, the mindshare of Redis is 5.7%, up from 0.0% compared to the previous year. The mindshare of ScyllaDB is 10.4%, up from 10.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases
 

Featured Reviews

Yaseer Arafat - PeerSpot reviewer
Unmatched Performance and Scalability for Modern Applications
Redis has room for improvement in a few areas. Enhanced tools for managing and monitoring clusters would be beneficial, as would built-in security mechanisms like advanced encryption and granular access controls. Simplifying setup and configuration could make Redis more accessible to new users. Introducing more enterprise-grade features, such as better multi-tenancy support and improved backup and restore capabilities, would also be advantageous. For the next release, it would be great to see enhanced cluster management tools, native multi-region supports for better data redundancy, integrated analytics for deeper insights, AI and ML integration features, and improved developer experience through enhanced SDKs and tools.
ArpitShah - PeerSpot reviewer
Self-hosting complexity and the way ScyllaDB counts operations can be confusing and may not reflect actual usage
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. The other problem is what they call. For example, they will say that for up to a million operations, you experience this. But the problem is if they have nine servers, then your one operation is counted as nine operations, not one. So, even though you have one write, they count it as nine. It's like it's just not false premises. You can always host it yourself, but then it's way more complex. The benefits are not substantially more than those of other databases. It's not that it's slow or anything. It's good enough and all. But it's just that ClickHouse or other databases are simpler and faster and probably provide more features. So, I kind of burn out from the database, and that's why I would keep it small.

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 in-memory data makes it fast."
"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's technical support team is good...The solution's initial setup process was straightforward."
"The performance of Redis is very fast."
"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."
"The product offers fast access to my database."
"It is particularly efficient for cloud-based storage and operations."
"I like how fast it is to query data from the ScyllaDB node!"
"The database is easy to use, fast, and accessible for applications because the API is straightforward."
"It is lightweight, and it requires less infrastructure."
"The documentation is good. It integrates easily with our existing data infrastructure."
"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 and scalability are good, and we hardly see any major issues with ScyllaDB."
"The product's most valuable features are efficiency and reliability."
"Firstly, if I update something, it's most likely to finish within milliseconds."
 

Cons

"Redis presents a single point of failure and lacks fault tolerance."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"The solution's pricing for a local installation is very expensive."
"There is a lack of documentation on the scalability of the solution."
"The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"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."
"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."
"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."
"Some of the regular commands in NoSQL do not work."
"The documentation is not well established for new developers."
"ScyllaDB needs to improve its handling of transactions."
"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."
"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."
 

Pricing and Cost Advice

"The tool is open-source. There are no additional costs."
"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."
"It's a bit expensive."
"It is an expensive tool compared to its competitor."
"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."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
848,253 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
15%
Educational Organization
7%
Manufacturing Company
6%
Computer Software Company
17%
Financial Services Firm
14%
Comms Service Provider
8%
Hospitality Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Redis?
Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you u...
What needs improvement with Redis?
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. Additionally, better documentation is neede...
What is your primary use case for Redis?
My primary use case for Redis has been leveraging it as a high-performance, in-memory data store to support real-time features in web applications. For instance, I use Redis to manage live chat sys...
What do you like most about Scylla?
The performance aspects of Scylla are good, as always... A good point about Scylla is that it can be used extensively.
What is your experience regarding pricing and costs for Scylla?
The enterprise version comes with a cost of about $300,000 per year, however, we did not experience the promised compaction benefits.
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...
 

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: April 2025.
848,253 professionals have used our research since 2012.