Problem
Paradox Shop's order-events stream needs several partitions for throughput, but without a partition key, an order's 'created' and 'cancelled' events could land on different partitions and be consumed out of order; a worker could end up processing a cancellation before it ever sees the order get created. Design a stream from scratch where 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.