AI Space

Data / Knowledge library

Apache Cassandra

a distributed wide-column nosql database

2026 · Daily Agent

Why learn Apache Cassandra?

Cassandra solves always-on, high-write, globally distributed data storage where horizontal scale, fault tolerance, and tunable consistency matter more than complex joins or strict single-node ACID behavior.

Where it came from

Created at Facebook by Avinash Lakshman and Prashant Malik (2008). Open-sourced by Facebook in 2008. Entered the Apache Incubator in 2009. Became an Apache Top-Level Project in 2010. Influenced by Amazon Dynamo (distribution) and Google Bigtable (data model).

Build your understanding

Work through these exercises in order. Try the task before opening a reference.

  1. Design a table for 'latest orders by user'. Pick partition key and clustering columns, then explain how your design avoids cross-partition scans.
  2. Run the same read/write flow with ONE, QUORUM, and ALL. Record latency and behavior after stopping one node. Summarize trade-offs in 5 bullets.
  3. Model IoT sensor events with TTL and day buckets. Implement insert + query for last 24 hours and explain hot-partition risk mitigations.
  4. Simulate node outage, recover it, then run validation steps (nodetool status, repair plan, read checks). Document what remained available and why.
  5. Compare primary-key query, materialized view, and SAI for one product-search scenario. Choose one and justify with expected read/write load.

More ways to practice

Level 1

Query-first data modeling

Design a table for 'latest orders by user'. Pick partition key and clustering columns, then explain how your design avoids cross-partition scans.

Level 2

Consistency tuning drill

Run the same read/write flow with ONE, QUORUM, and ALL. Record latency and behavior after stopping one node. Summarize trade-offs in 5 bullets.

Level 3

Time-series retention pattern

Model IoT sensor events with TTL and day buckets. Implement insert + query for last 24 hours and explain hot-partition risk mitigations.

Level 4

Failure simulation and repair basics

Simulate node outage, recover it, then run validation steps (nodetool status, repair plan, read checks). Document what remained available and why.

Level 5

Indexing decision memo

Compare primary-key query, materialized view, and SAI for one product-search scenario. Choose one and justify with expected read/write load.

Documentation and sources

Catalog research notes

Connect the ideas

Alternatives

ScyllaDB

Explore next

ScyllaDBAmazon DynamoDBApache SparkRedis

Catalog source: technology-maxxing. This page reproduces the existing catalog’s learning material and source links.