Before we discuss its relevance, let us understand the 3 basic processes of its system:
- The Architecture of Cassandra
The primary architecture of Cassandra consists of a cluster of nodes. It is structured as a peer-to-peer system and closely resembles DynamoDB and Google Bigtable. The great part about Cassandra’s architecture is that it can easily expand to accommodate more data. Adding more nodes can increase the amount of data the system needs to carry. Developers can also shrink the database system by reducing the number of nodes. Cassandra’s architecture gives it a considerable edge compared to previous SQL databases, as it can handle data-carrying capacity with utmost ease and perfection.
- Partitioning System
In Cassandra, data is stored and retrieved using a partitioning system. A partitioner decides where the primary copy of a data set is stored. Every node is responsible for a set of tokens based on a partition key. The partition key allows you to determine where the data is stored.
- Replication Process
Cassandra works on data replication across nodes. The secondary nodes are called replica nodes, and the number of replica nodes for a given data set depends on the Replication Factor (RF). A replication factor of 2 means both the nodes cover the same token range and store the same data. Even when one node stops functioning, temporarily or permanently, other nodes hold the same data, which means the data is never lost in such a scenario.
Before we discuss its relevance, let us understand the 3 basic processes of its system:
- The Architecture of Cassandra
The primary architecture of Cassandra consists of a cluster of nodes. It is structured as a peer-to-peer system and closely resembles DynamoDB and Google Bigtable. The great part about Cassandra’s architecture is that it can easily expand to accommodate more data. Adding more nodes can increase the amount of data the system needs to carry. Developers can also shrink the database system by reducing the number of nodes. Cassandra’s architecture gives it a considerable edge compared to previous SQL databases, as it can handle data-carrying capacity with utmost ease and perfection.
- Partitioning System
In Cassandra, data is stored and retrieved using a partitioning system. A partitioner decides where the primary copy of a data set is stored. Every node is responsible for a set of tokens based on a partition key. The partition key allows you to determine where the data is stored.
- Replication Process
Cassandra works on data replication across nodes. The secondary nodes are called replica nodes, and the number of replica nodes for a given data set depends on the Replication Factor (RF). A replication factor of 2 means both the nodes cover the same token range and store the same data. Even when one node stops functioning, temporarily or permanently, other nodes hold the same data, which means the data is never lost in such a scenario.