Events are named as facts, in the past tense
An event name says what happened (OrderPlaced), not what someone should do (CreateOrder).
MediumChecked automatically
- Applies to:
- Services that publish events
- Rule id:
- events.names-are-facts
Why it matters
An event reports something that already happened. A command asks for something to happen. When a topic carries a name like CreateOrder, the publisher is telling consumers what to do, so it has to know who they are and what they do. That is the coupling events were meant to remove. Readers also can't tell whether the thing happened or was only requested.
How to apply it
- Name each event with a noun and a past participle:
OrderPlaced,PaymentCaptured. - Use business language.
OrderRowUpdateddescribes a table, not something the business cares about. - Publish one event per fact. A catch-all
OrderChangedforces every consumer to work out what changed. - If you need a specific service to do something, that is a command: call that service or send to its queue.
Example
Facts: OrderPlaced, PaymentCaptured, ShipmentDelayed. Not facts: CreateOrder, ProcessPayment, OrderUpdate.
References
Checklists with this rule
Related agent skill: designing-domain-events