Designing an event: purpose, consumption and content
Before designing an event, decide what it is for, how it will be consumed and what it should carry, and remember whose story it tells.
Software, mostly
I write about software development. Not often: only when I feel like it and when I think I have something worth sharing.
Recent
Before designing an event, decide what it is for, how it will be consumed and what it should carry, and remember whose story it tells.
Queues forget messages, streams keep them, and the way you consume them decides whether you keep the order, the scale or most of both.
Commands and events travel through the same pipes, but they differ in intent, audience and, above all, in who owns the contract. Event Storming helps you find the stories your business tells, and bounded contexts tell you who owns each one.
Why "you don't need a harness" makes sense for someone working on frontier models, but not as general advice, and which parts of a harness are worth keeping.
Sometimes we don't need ultra-sophisticated machinery to run a discovery exercise on legacy software, and AI can be a great help.
Events can reduce coupling, absorb load and help systems scale, but you pay for them in complexity.