Cassandra easy
According to the CAP Theorem, Cassandra is primarily classified as an 'AP' system. What does 'AP' emphasize in the event of a network failure?
- A It prioritizes strict mathematical Consistency across all nodes, even if it means rejecting incoming writes.
- B It prioritizes Availability and Partition Tolerance, ensuring the database remains writable even if part of the network is down, at the cost of potential temporary inconsistency.
- C It prioritizes Absolute Privacy, ensuring that data is encrypted even if the servers are seized.
- D It prioritizes Atomic Processing, guaranteeing that every single transaction is 100% ACID compliant across all tables.
Answer: B. It prioritizes Availability and Partition Tolerance, ensuring the database remains writable even if part of the network is down, at the cost of potential temporary inconsistency.
In a distributed system, network 'Partitions' are inevitable. Cassandra chooses to keep the 'Store' open for business (Availability). It will accept writes even if it can't talk to all replicas immediately, fixing the data later via mechanisms like 'Hinted Handoff' and 'Read Repair'.
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?
- Unlike a Leader-Follower architecture (like MySQL or Redis), how does Cassandra maintain high availability within its node cluster?
- 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?