Modeling for the queries you actually run

An identity services provider had modeled Cassandra tables the way it would have modeled relational ones, then added secondary indexes to cover the queries the primary key did not serve. Some partitions had grown into the gigabytes, and index-backed queries fanned out to every node in the ring. AceMQ was engaged to redesign the model.

Apache Cassandra on Kubernetes backing identity verification and credential lifecycle services.

AceMQ inventoried every query the application issued and worked backward to the tables required to serve them, accepting denormalization where it removed fan-out. Partition sizing was projected against several years of growth rather than current volume, and the migration was designed to run with dual writes so cutover carried no window.

• 1
  Inventoried actual application query patterns and derived the required table designs from them
• 2
  Introduced time and hash bucketing to bound partition growth against multi-year projections
• 3
  Replaced secondary index queries with purpose-built denormalized tables to eliminate cluster-wide fan-out
• 4
  Chose clustering keys and ordering to serve range scans and pagination without in-memory sorting
• 5
  Designed a dual-write and backfill migration path so the cutover required no write freeze
• 6
  Set partition size and row count guardrails with monitoring to catch regressions in future development