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

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
5th
Average Rating
8.0
Reviews Sentiment
6.0
Number of Reviews
25
Ranking in other categories
Vector Databases (12th)
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 July 2026, in the NoSQL Databases category, the mindshare of Cassandra is 8.2%, down from 10.4% compared to the previous year. The mindshare of ScyllaDB is 6.1%, down from 10.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
Cassandra8.2%
ScyllaDB6.1%
Other85.7%
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.
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

"If you need availability and consistency, you can go with Cassandra."
"The most valuable features of Cassandra are its scaling capabilities and its non-SQL nature capabilities."
"Can achieve continuous data without a single downtime because of node to node ring architecture."
"Cassandra offers high availability and fault tolerance, making it suitable for large-scale data storage and real-time processing."
"Based on my experience, Cassandra is good for document management system, as well as distributed database system, and the automatic recovery process is there."
"Setup was very straightforward."
"Some of the valued features of this solution are it has good performance and failover."
"A consistent solution."
"It is lightweight, and it requires less infrastructure."
"The product's most valuable features are efficiency and reliability."
"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."
"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."
"The documentation is good. It integrates easily with our existing data infrastructure."
"Firstly, if I update something, it's most likely to finish within milliseconds."
 

Cons

"Fine-tuning was a bit of a challenge."
"There could be more integration, and it could be more user-friendly."
"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."
"The disc space is lacking. You need to free it up as you are working."
"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."
"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."
"We found some issues with the batch inserts when the data volume is large."
"The solution doesn't have joins between tables so you need other tools for that."
"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 is not well established for new developers."
"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 of Scylla is an area with shortcomings and needs to be improved."
"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."
"ScyllaDB needs to improve its handling of transactions."
 

Pricing and Cost Advice

"I use the tool's open-source version."
"Cassandra is a free open source solution, but there is a commercial version available called DataStax Enterprise."
"There are licensing fees that must be paid, but I'm not sure if they are paid monthly or yearly."
"We pay for a license."
"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."
"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 a bit expensive."
"I believe that there is a yearly licensing cost and that it's expensive."
"It is an expensive tool compared to its competitor."
"It's free."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
903,933 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
8%
Comms Service Provider
7%
Performing Arts
6%
Outsourcing Company
12%
Financial Services Firm
8%
Comms Service Provider
8%
Transportation Company
7%
 

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 Business3
Midsize Enterprise2
Large Enterprise8
 

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 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

 

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: June 2026.
903,933 professionals have used our research since 2012.