Stream design workspace / Reading notes
Ordering and partition boundaries
Choose the smallest ordering guarantee the domain requires.
Find the consistency unit
Determine which events must be processed in order for one entity. A partition key should reflect that unit rather than a random transport detail.
Plan for uneven keys
Some entities may produce far more events than others. Measure key distribution and avoid assuming that more partitions will fix a single hot key.
Define late-event behaviour
Document how consumers handle delayed or stale versions. A consumer should not silently overwrite a newer state with an older event.