Problem
Paradox Shop's checkout service needs to call inventory, pricing, loyalty, recommendations, and analytics, but calling all five synchronously in a single request means any one of them slowing down blocks the entire checkout. Inventory and pricing genuinely have to complete before checkout can proceed; loyalty, recommendations, and analytics don't gate the order at all, so none of those three should be able to stall checkout by running slow. Design the call graph from scratch: keep only the truly required calls synchronous, and route the optional ones through async messaging so a slow optional dependency can never stall checkout.