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.