Cassandra medium
To prevent a single Partition (e.g., `Sensor_ID: 101`) from becoming infinitely large over time, a developer adds a time component to the key: `((Sensor_ID, Day_Bucket), Reading_Timestamp)`. What is this pattern called?
- A Vertical Sharding: Splitting columns into separate databases.
- B Bucketing: Artificially splitting a single logical partition across multiple physical partitions to keep them manageable.
- C Data Archiving: Moving old partitions to a cold-storage cluster.
- D Normalizing: Moving the data into a relational table to save space.
Answer: B. Bucketing: Artificially splitting a single logical partition across multiple physical partitions to keep them manageable.
This is the most common way to handle Time Series data. By adding a 'Bucket' (like Day, Week, or Month) to the Partition Key, you cap the size of any individual partition. This prevents the 'Wide Partition' performance issues while keeping the data queryable.
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?