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.