Problem
Paradox Shop's product catalog now serves 2,000 requests/second at the application tier, generating 70,000 database reads/second against 800 writes/second underneath. The app tier was sized for launch-day traffic, and everything still lands on one oversized database with no read/write split; it's CPU-bound on read traffic alone. Resize the fleet, and split reads onto dedicated replicas while keeping writes on a single primary.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.