Why fit Cassandra to a high-read, high-write workload?

WHAT THIS TESTS This assesses whether you can connect a specific database's architecture to a workload profile, and whether you understand the trade-offs Cassandra makes to achieve write and read scalability.

A GOOD ANSWER COVERS Cassandra partitions data with consistent hashing over a token ring, so each row maps by partition key to a node, distributing both storage and request load evenly and allowing linear scale-out by adding nodes. Its masterless, peer-to-peer design means every replica can accept reads and writes, removing the single-leader write bottleneck and keeping the system available when nodes fail. The write path is log-structured: appends go to a commit log and an in-memory memtable, flushed later to immutable SSTables, which makes writes very fast and sequential. Replication places copies on multiple nodes across racks or data centers. Tunable consistency lets each query pick a level, from ONE for speed to QUORUM or ALL for stronger guarantees, so you balance latency and freshness per operation. A user profile service, keyed by user id with mostly point lookups and frequent updates, fits this model precisely.

COMMON WRONG ANSWERS Expecting relational features like arbitrary joins or normalized schemas; Cassandra demands query-first denormalized modeling. Assuming strong consistency by default, when the default is tunable and often eventual. Ignoring that secondary indexes and large partitions can become performance traps.

LIKELY FOLLOW-UPS How does QUORUM read plus QUORUM write achieve strong consistency? What is a hot partition and how do you avoid it? How does compaction work? What problems do tombstones and wide partitions cause?

ONE CONCRETE EXAMPLE Model the profiles table with the user id as the partition key so each profile is a single-partition read and write. With replication factor three and QUORUM on both reads and writes, you get strong consistency while still tolerating one node failure, and the ring spreads millions of concurrent profile updates across the cluster.