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

Cassandra 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

Cassandra
Ranking in NoSQL Databases
4th
Average Rating
8.0
Reviews Sentiment
6.1
Number of Reviews
23
Ranking in other categories
Vector Databases (15th)
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 Cassandra is 10.8%, down from 12.8% 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

Himanshu Amodwala - PeerSpot reviewer
Well-equipped to handle a massive influx of data and billions of requests
The use of Cassandra in real-time data analytics has been pivotal for our e-commerce platform. As our platform operates 24/7, providing services to sellers and customers alike, the need for real-time updates is paramount. For instance, when a customer leaves comments or feedback on an image, they anticipate an immediate reflection of these changes on the portal. Similarly, sellers altering product attributes or updating images expect instant visibility of these modifications. Handling large data volumes with Cassandra has been an excellent experience. Despite challenges related to the influx, these were not attributed to Cassandra itself but rather to middle-layer issues. Generally, it demonstrated scalability with workloads, thanks to its horizontal scaling capabilities. We could easily add new nodes to the system as needed, ensuring the platform coped well with increasing loads. The tool's most beneficial feature for scalability is its entire architecture. The absence of a single point of failure or a leader within the ecosystem contributes to its robust scalability. This key aspect influenced our decision to opt for the Cassandra ecosystem. In terms of performance, it demonstrated the ability to handle approximately 1.6 billion requests per day. This was achieved on AWS using EC2 instances, and it was during a period about four to five years ago.
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

"The most valuable features of Cassandra are its scaling capabilities and its non-SQL nature capabilities."
"Overall, I would rate Cassandra as nine because of its fast writes, which really suit our use cases mostly."
"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."
"Its retrieval is similar to an RDBMS, so our team finds it easy to adapt."
"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."
"The most valuable features of this solution are its speed and distributed nature."
"The most valuable features of Cassandra are the NoSQL database, high performance, and zero-copy streaming."
"Some of the valued features of this solution are it has good performance and failover."
"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 database is easy to use, fast, and accessible for applications because the API is straightforward."
"It is lightweight, and it requires less infrastructure."
"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."
"The performance aspects of Scylla are good, as always... A good point about Scylla is that it can be used extensively."
"ScyllaDB is very fast, and I can use it for so many things."
"ScyllaDB is fast and reliable. It has good performance."
"The performance and scalability are good, and we hardly see any major issues with ScyllaDB."
 

Cons

"There were challenges with the query language and the development interface. The query language, in particular, could be improved for better optimization. These challenges were encountered while using the Java SDK."
"The solution is limited to a linear performance."
"Batching bulk data can cause performance issues."
"Doesn't support a solution that can give aggregation."
"We found some issues with the batch inserts when the data volume is large."
"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."
"There could be more integration, and it could be more user-friendly."
"Maybe they can improve their performance in data fetching from a high volume of data sets."
"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."
"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."
"ScyllaDB needs to improve its handling of transactions."
"From a sales pitch standpoint, it needs to deliver on promises of better ROI and compaction."
"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."
"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."
 

Pricing and Cost Advice

"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."
"I use the tool's open-source version."
"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."
"We pay for a license."
"It's a bit expensive."
"It is an expensive tool compared to its competitor."
"I believe that there is a yearly licensing cost and that it's 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."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
845,040 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
15%
Healthcare Company
5%
Manufacturing Company
5%
Computer Software Company
18%
Financial Services Firm
14%
Comms Service Provider
7%
Hospitality Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Cassandra?
The use of Cassandra in real-time data analytics has been pivotal for our e-commerce platform. As our platform operates 24/7, providing services to sellers and customers alike, the need for real-ti...
What needs improvement with Cassandra?
Cassandra is very complex to manage. Sometimes, I need to involve a senior DevOps engineer if we encounter a problem. About a year ago, we were unable to recover data without help from a senior Dev...
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

 

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