Problem
Paradox Shop's B2B order API already routes correctly through a connection pool at 1,200 RPS. The cluster underneath is sharded by tenant_id alone, and one enterprise customer generating 40% of all 30,000 writes/sec sends every one of those writes to the same shard, melting it, no matter how many shards exist. Fix the partition key so a single large tenant can't overwhelm one shard, without touching the pooled path above it.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.