Problem
Paradox Shop's order API must serve 800 RPS against a relational order schema for customers, orders, line items, and payments; the order-history lookup by customer must stay fast against 40 million orders. Build the application tier the API needs, model the four tables' entities and relationships so the data itself can't go inconsistent, and index the field that lookup actually depends on.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.