Problem
Paradox Shop's reporting module; nightly and on-demand sales reports; must never share a deploy fleet or scaling pool with checkout. Checkout's traffic is steady and predictable; reporting's is spiky, CPU-heavy, and completely unrelated: if the two shared instances, a big report run would compete with checkout for capacity during a traffic spike of its own. Design the service boundary from scratch: reporting gets its own independently-scaled pool, sized for its own profile, so a report spike can never take capacity away from checkout.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.