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

Cassandra

3.6K
3.5K
+ 1
507
Galera Cluster

55
102
+ 1
0
Add tool

Cassandra vs Galera Cluster: What are the differences?

1. Scalability: Cassandra is designed for high scalability by distributing data across multiple nodes in a cluster, allowing linear scalability for both read and write operations. Galera Cluster, on the other hand, is a synchronous replication solution that can have limitations in scaling due to the need for all nodes to commit transactions in a multi-master setup.

2. Consistency: Cassandra offers tunable consistency levels, enabling users to choose between strong consistency and high availability. Galera Cluster enforces strict synchronous replication, ensuring strong consistency across all nodes but potentially impacting performance in certain scenarios.

3. Data Replication: In Cassandra, data replication is achieved through the replication factor and consistency level settings, allowing for control over data durability and availability. Galera Cluster replicates data synchronously across all nodes, ensuring that each node holds a copy of the same data at all times.

4. Partitioning: Cassandra uses consistent hashing to partition data across nodes, providing efficient distribution and retrieval of data. Galera Cluster does not support automatic data partitioning and relies on traditional sharding methods for horizontal scaling.

5. Conflict Resolution: In Cassandra, conflict resolution is handled through timestamps and client-provided timestamps, resolving conflicts based on the latest timestamp. Galera Cluster resolves conflicts at the network level, requiring strict consistency to avoid conflicts among nodes.

6. High Availability: Cassandra provides built-in fault tolerance through data replication and automatic data repair mechanisms. Galera Cluster relies on synchronous replication for high availability, which can introduce latency and performance trade-offs in certain scenarios.

In Summary, Cassandra focuses on scalability and flexibility in data distribution, while Galera Cluster prioritizes strong consistency and data integrity in a multi-master setup.

Advice on Cassandra and Galera Cluster
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
Pankaj Soni
Chief Technical Officer at Software Joint · | 2 upvotes · 172.8K 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
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
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Cassandra
Pros of Galera Cluster
  • 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
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of Cassandra
    Cons of Galera Cluster
    • 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

      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 Galera Cluster?

      It’s an easy-to-use, high-availability solution, which provides high system up-time, no data loss and scalability for future growth. You can Keep it up and running 24/7. Putting our expertise to use will help you avoid trial and error.

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

      What companies use Cassandra?
      What companies use Galera Cluster?
      Manage your open source components, licenses, and vulnerabilities
      Learn More

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

      What tools integrate with Cassandra?
      What tools integrate with Galera Cluster?

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

      Blog Posts

      What are some alternatives to Cassandra and Galera Cluster?
      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