Representative engagement template — replace with a publishable client narrative when ready.
The original shard key concentrated writes on the most recent calendar period, producing jumbo chunks every quarter. We modeled the access pattern, proposed a hashed shard key over a stable composite, and rehearsed the live re-shard against a staging copy of the cluster.
Outcomes
- Hashed shard key replaced range key
- Live re-sharding rehearsed in staging
- Cutover ran with zero application downtime