Problem
Paradox Shop's order-events stream below has no partition key and a single partition; every event, for every order, is jammed into one lane. Worse, without a key, an order's 'created' and 'cancelled' events aren't even guaranteed to land together once the stream is split up properly. A worker recently processed a cancellation before it ever saw the matching order get created. Fix the stream so every event for the same order is guaranteed to arrive in order, without serializing unrelated orders behind each other.
Required components
Click to add a component to the canvas.
Additional components
Browse by category. Click or drag a component onto the canvas.