Need advice about which tool to choose?Ask the StackShare community!

Cassandra

3.6K
3.5K
+ 1
507
ScyllaDB

131
182
+ 1
8
Add tool

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.

Advice on Cassandra and ScyllaDB
Vinay Mehta
Needs advice
on
CassandraCassandra
and
ScyllaDBScyllaDB

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.

See more
Replies (4)
Recommends
on
ScyllaDBScyllaDB

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

See more
Alex Peake
Recommends
on
CassandraCassandra

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.

See more
Recommends
on
ScyllaDBScyllaDB

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.

See more
Pankaj Soni
Chief Technical Officer at Software Joint · | 2 upvotes · 145.4K views
Recommends
on
CassandraCassandra

i love syclla for pet projects however it's license which is based on server model is an issue. thus i recommend cassandra

See more
Decisions about Cassandra and ScyllaDB
Tom Klein

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.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Cassandra
Pros of ScyllaDB
  • 119
    Distributed
  • 98
    High performance
  • 81
    High availability
  • 74
    Easy scalability
  • 53
    Replication
  • 26
    Reliable
  • 26
    Multi datacenter deployments
  • 10
    Schema optional
  • 9
    OLTP
  • 8
    Open source
  • 2
    Workload separation (via MDC)
  • 1
    Fast
  • 2
    Replication
  • 1
    Fewer nodes
  • 1
    Distributed
  • 1
    Scale up
  • 1
    High availability
  • 1
    Written in C++
  • 1
    High performance

Sign up to add or upvote prosMake informed product decisions

Cons of Cassandra
Cons of ScyllaDB
  • 3
    Reliability of replication
  • 1
    Size
  • 1
    Updates
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is Cassandra?

    Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

    What is ScyllaDB?

    ScyllaDB is the database for data-intensive apps that require high performance and low latency. It enables teams to harness the ever-increasing computing power of modern infrastructures – eliminating barriers to scale as data grows.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Cassandra?
    What companies use ScyllaDB?
    See which teams inside your own company are using Cassandra or ScyllaDB.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Cassandra?
    What tools integrate with ScyllaDB?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to Cassandra and ScyllaDB?
    HBase
    Apache HBase is an open-source, distributed, versioned, column-oriented store modeled after Google' Bigtable: A Distributed Storage System for Structured Data by Chang et al. Just as Bigtable leverages the distributed data storage provided by the Google File System, HBase provides Bigtable-like capabilities on top of Apache Hadoop.
    Google Cloud Bigtable
    Google Cloud Bigtable offers you a fast, fully managed, massively scalable NoSQL database service that's ideal for web, mobile, and Internet of Things applications requiring terabytes to petabytes of data. Unlike comparable market offerings, Cloud Bigtable doesn't require you to sacrifice speed, scale, or cost efficiency when your applications grow. Cloud Bigtable has been battle-tested at Google for more than 10 years—it's the database driving major applications such as Google Analytics and Gmail.
    Hadoop
    The Apache Hadoop software library is a framework that allows for the distributed processing of large data sets across clusters of computers using simple programming models. It is designed to scale up from single servers to thousands of machines, each offering local computation and storage.
    Redis
    Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.
    Couchbase
    Developed as an alternative to traditionally inflexible SQL databases, the Couchbase NoSQL database is built on an open source foundation and architected to help developers solve real-world problems and meet high scalability demands.
    See all alternatives