TrackSSA0063

Too Many Tiny Services

Hard

Problem

Paradox Shop's checkout flow breaks down into 9 logical steps: validate cart, check inventory, apply pricing rules, apply promotions, check fraud, reserve stock, charge payment, write the order, and send a confirmation event. Built naively as 9 separate microservices chained one after another, that's 9x a network round trip added to every checkout, on top of 9x the operational surface area. Design a leaner chain from scratch: consolidate down to 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.

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.