Need advice about which tool to choose?Ask the StackShare community!
Cassandra vs Scylla: What are the differences?
Introduction
Cassandra and Scylla are two popular NoSQL databases that are widely used for handling large amounts of data. While they share similarities, there are key differences between the two that make them suitable for different use cases.
1. Data Model: Cassandra follows a columnar storage model where data is organized in tables with flexible schemas. It allows for the storage of different types of columns within a row. On the other hand, Scylla is based on Cassandra's distributed design and provides a column-family data model, which is similar to Cassandra's, but with additional optimizations for performance.
2. Scalability: Cassandra is known for its excellent scalability and high availability. It can distribute data across multiple nodes in a cluster, allowing for horizontal scalability. Scylla takes Cassandra's scalability to the next level by being built from the ground up in C++. It leverages modern hardware and advanced techniques to provide exceptional throughput and low latency even under heavy workloads.
3. Performance: While both Cassandra and Scylla offer high performance, Scylla is specifically designed to achieve maximum performance. Scylla achieves this by using a shared-nothing architecture, which means that each node operates independently, resulting in reduced coordination overhead and faster response times. Scylla's write and read paths are highly optimized, resulting in significantly lower latencies compared to Cassandra.
4. Compatibility: Cassandra has been widely adopted and has a well-established ecosystem. It has a large community and supports a variety of client libraries and tools. Scylla, being compatible with Cassandra's API, can seamlessly replace Cassandra in most use cases. It provides drop-in compatibility, allowing users to migrate from Cassandra to Scylla without code changes.
5. Ease of Use: While both databases require some level of expertise to manage, Cassandra tends to have a steeper learning curve. Setting up and optimizing a Cassandra cluster can be challenging, especially for inexperienced users. Scylla simplifies this process by automating many of the manual tasks and providing a user-friendly management interface, making it easier to get started and operate.
6. Community Support: Cassandra has a vibrant and active community that has contributed to its growth and adoption. It has been around for a longer time and has a larger user base. Scylla, being a younger project, has a smaller community compared to Cassandra. However, Scylla's community is growing rapidly, and it benefits from Cassandra's vast ecosystem and community knowledge.
In Summary, Cassandra and Scylla have key differences including their data models, scalability, performance, compatibility, ease of use, and community support. Each database offers unique advantages and is suitable for different use cases.
The problem I have is - we need to process & change(update/insert) 55M Data every 2 min and this updated data to be available for Rest API for Filtering / Selection. Response time for Rest API should be less than 1 sec.
The most important factors for me are processing and storing time of 2 min. There need to be 2 views of Data One is for Selection & 2. Changed data.
Scylla can handle 1M/s events with a simple data model quite easily. The api to query is CQL, we have REST api but that's for control/monitoring
Cassandra is quite capable of the task, in a highly available way, given appropriate scaling of the system. Remember that updates are only inserts, and that efficient retrieval is only by key (which can be a complex key). Talking of keys, make sure that the keys are well distributed.
i love syclla for pet projects however it's license which is based on server model is an issue. thus i recommend cassandra
By 55M do you mean 55 million entity changes per 2 minutes? It is relatively high, means almost 460k per second. If I had to choose between Scylla or Cassandra, I would opt for Scylla as it is promising better performance for simple operations. However, maybe it would be worth to consider yet another alternative technology. Take into consideration required consistency, reliability and high availability and you may realize that there are more suitable once. Rest API should not be the main driver, because you can always develop the API yourself, if not supported by given technology.
The Gentlent Tech Team made lots of updates within the past year. The biggest one being our database:
We decided to migrate our #PostgreSQL -based database systems to a custom implementation of #Cassandra . This allows us to integrate our product data perfectly in a system that just makes sense. High availability and scalability are supported out of the box.
Pros of Cassandra
- Distributed119
- High performance98
- High availability81
- Easy scalability74
- Replication53
- Reliable26
- Multi datacenter deployments26
- Schema optional10
- OLTP9
- Open source8
- Workload separation (via MDC)2
- Fast1
Pros of ScyllaDB
- Replication2
- Fewer nodes1
- Distributed1
- Scale up1
- High availability1
- Written in C++1
- High performance1
Sign up to add or upvote prosMake informed product decisions
Cons of Cassandra
- Reliability of replication3
- Size1
- Updates1
Cons of ScyllaDB
Sign up to add or upvote consMake informed product decisions
What is Cassandra?
What is ScyllaDB?
Need advice about which tool to choose?Ask the StackShare community!
What companies use ScyllaDB?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with ScyllaDB?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+5
+17
+42
+26