Problem
Paradox Shop needs an order-event pipeline that serves two very different consumers off the same 600 events/sec stream: fulfillment must process every event in realtime to ship orders on time, while analytics runs nightly batch jobs that can fall six or more hours behind. Design the topology from scratch so each subscriber gets its own independent capacity, and analytics can lag for hours without blocking fulfillment or losing events.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.