Problem
Paradox Shop needs order events, customer events, and inventory events routed so each consumer only ever sees its own category, not a generic feed it has to filter down to the one-third it actually cares about. A spike in any one category shouldn't be able to slow down consumers that only wanted the others. Design a topology from scratch that splits events into one topic per category, so each consumer only ever receives what's relevant to it.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.