ProblemsFTS0063

Too Many Tiny Services

Hard

Problem

A single checkout request at Paradox Shop hops through the 9 microservices below end to end; validate cart, check inventory, apply pricing rules, apply promotions, check fraud, reserve stock, charge payment, write the order, and send a confirmation event; each its own network call, chained one after another. The hops alone add 9x a network round trip to every checkout, on top of 9x the operational surface area. Fix it: consolidate down to a lean chain of at most 3 hops end to end, but keep the one workload that genuinely needs to scale independently of the rest (the bursty, CPU-heavy fraud-check step) as its own separately-scaled piece.

Required components

Click to add a component to the canvas.

Additional components

Browse by category. Click or drag a component onto the canvas.

Current Production Metrics
Snapshot of the system before any changes.
Traffic
500 RPS
Monthly cost
$2,970

Drag components from the library onto the canvas, then drag from a component's right handle to connect it to another.

100%

Design canvas

Sign up to start designing

Sign up free

Premium is free for 58 more days.