Problem
Paradox Shop's B2B order API serves 1,200 requests/second through a pooled connection to a sharded orders cluster. One enterprise customer alone generates 40% of all 30,000 writes/sec; partitioning by tenant_id alone would send every one of that tenant's writes to the same shard, no matter how many shards exist. Build the pooled write path, and design a partition key that doesn't let a single large tenant overwhelm one shard.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.