Problem
Paradox Shop's order-history API must serve 800 RPS. Its orders table has grown to 40 million rows, and two queries against it have slowly degraded into full table scans: order history filtered by customer_id, and a recent-orders dashboard filtered by created_at. Build the application tier the API needs, and get both access patterns fast again without blowing the write-throughput or storage budget the two now share.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.