5 exercises — Learn the vocabulary of event storming workshops: domain events, commands, aggregates, policies, and hotspots.
0 / 5 completed
1 / 5
In event storming, domain events are always named:
Domain events represent something that has already happened — they are facts about the past. Past tense naming ('OrderPlaced', 'UserRegistered') makes this explicit and distinguishes them from commands.
2 / 5
In event storming notation, a command represents:
Commands are intentions or requests: 'PlaceOrder', 'CancelSubscription'. They are issued by actors or policies and, when processed by an aggregate, cause domain events to be emitted.
3 / 5
Which definition best describes a policy in event storming?
Policies (often represented as purple stickies) capture reactive business rules: 'whenever PaymentFailed, send a NotifyCustomer command'. They encode the 'if event → then command' logic of the business.
4 / 5
A hotspot during an event storming session is:
Hotspots (red stickies) are placed where participants disagree, where the domain is poorly understood, or where technical/business complexity is high. They become the agenda for follow-up deep-dive sessions.
5 / 5
What is the role of a read model in an event storming diagram?
Read models (query-side projections) represent the information visible to an actor when deciding whether to issue a command — e.g., 'the order summary screen' that a user sees before clicking 'Cancel Order'.