Cassandra easy
Unlike a Leader-Follower architecture (like MySQL or Redis), how does Cassandra maintain high availability within its node cluster?
- A It uses a centralized 'Master' node that handles all schema updates and data deletions.
- B It employs a Peer-to-Peer (Masterless) architecture where every node is equal and capable of serving both read and write operations.
- C It relies on a specialized hardware load balancer to perform leader election every 60 seconds.
- D All write operations are sent to a 'Shadow Cluster' before being committed to the main cluster.
Answer: B. It employs a Peer-to-Peer (Masterless) architecture where every node is equal and capable of serving both read and write operations.
Cassandra has no 'Single Point of Failure'. Because it is masterless, any node in the cluster can accept a request from a client. If one node fails, the cluster remains functional because the other nodes hold replicas of the data and can continue to serve requests.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- In a Cassandra Keyspace, what does a 'Replication Factor of 3' specifically guarantee for your data redundancy?
- Cassandra Query Language (CQL) looks similar to SQL. What is a fundamental SQL feature that CQL does NOT support to ensure distributed performance?
- What is the critical architectural function of the 'Partition Key' in a Cassandra table?
- Apache Cassandra is fundamentally designed as which architectural category of NoSQL database?
- An extreme financial trading application requires 'Batch' sync for the Commit Log. What is the fundamental throughput limitation introduced by this setting?
- In a cluster with high 'Mutation' (Write) frequency, why is the `Row Cache` almost universally disabled by experts?