Question
Choose a real business event and sketch its purpose, key, essential fields, and consumers. The community can help you reason about partitioning, schemas, delivery semantics, and safe evolution.
1 answer
Name the event as a completed business fact, then choose a stable key that keeps related events ordered. Include an event ID, event time, schema version, producer, and the smallest useful business payload. Document compatibility expectations before adding consumers, and design consumption to be idempotent so replay is safe.