Used to identify Domain Events
Domain Event represents a change in the system.
Events must have a subject (noun) and a predicate (verb).
Verb must be past tense indicating somethiing has alredy happened.
External systems can also produce domain events.
Domain evnts must follow a timeline.
Example:
User Registered
User Group Changed
If you see an ambiguity during the identification of Domain Events, mark the spot with the Pink Stiker.
The decision on correct or correct order of domain event can be postponed to later.
These are the third party systems that your Domain Events can go to.
Commands are the intents of users
Commands are something that changes the state of the system.
Something that our users look at before asking the system to do something or send a command.
These are the screens of our application.
They Execute the commands
We need to understand which role is the system is running the command
Example:
-Administratir -Reviewer -Editor
The Policies subscribe to domain events.
When it receives a domain event, it sents another command to complement the work.
Example:
When a user accepts the invitation to join, the invitee gets a mail notification.
- Modelling Reactive Systems with Event Storming and Domain-Driven Design
- Event Storming and Spring with a Splash of DDD
- Design Level EventStorming
- A facilitators recipe for Event Storming
- A step by step guide to Event Storming – our experience
- Event Storming and Modeling
- Misadventures with Big Design Up Front
- Remote Team Flow EventStorming for Retrospectives
- EventStorming; Core concepts, glossary and legend
- Event storming recipes
- Model storming
- 50.000 orange stickies later
- EVENT STORMING - COLLABORATIVE LEARNING FOR COMPLEX DOMAINS
- Transactions redefined
- Alberto Brandolini - 50,000 Orange Stickies Later
- YOW! 2016 Paul Rayner - EventStorming - Collaborative Learning for Complex Domains
- Trying out online EventStorming
- Hands-On Domain-Driven Design with .NET Core, Chapter 3: Event Stroming, Alexey Zimarev
- Introducing EventStorming, Alberto Brandolini
- Domain-Driven Design Distilled, Chapter 7: Acceleration and Management Tools, Vaughn Vernon
- The EventStorming Handbook, Paul Rayner
- What is Domain-Driven Design?, Chapter 8: Event Storming, Vladik Khononov
mariuszgil / awesome-eventstorming for providing the information to start this repository.