EventStorming Fundamentals Course
Everything about EventStorming with examples
1.1. Index
1.2. The origin of EventStorming
FREE PREVIEW1.3. Introduction to Domain-Driven Design
1.4. Some essential Domain-Driven Design concepts
1.5. Difference between domain and business
1.6. The journey of EventStorming (past and present)
1.7. EventStorming books
1.8. EventStorming popularity
1.9. Who is using EventStorming?
1.10. What is EventStorming?
1.11. Why EventStorming?
1.12. For who is EventStorming?
Self-assessment quizz
Feedback: satisfaction survey
EventStorming fields of application
Self-assessment quizz
Feedback: satisfaction survey
3.1. Index
3.2. Scope
3.3. The key ingredients
3.4. The importance of the facilitator
FREE PREVIEW3.5. Invitations phase
3.6. Room setup phase
3.7. Kick-off phase
3.8. Chaotic exploration phase
3.9. Enforcing the timeline phase
3.10. People and Systems phase
3.11. Explicit walk-through phase
3.12. Reverse narrative phase
3.13. Value created and destroyed phase
3.14. Problems and Opportunities phase
3.15. Pick the right problem phase
3.16. Discover Subdomains and Bounded Contexts phase
3.17. Wrapping up phase
Self-assessment quizz
Feedback: satisfaction survey
4.1. Introduction
4.2. Opening strategies
4.3. Midpoint strategies
4.4. Notation
4.5. Notation: Domain Event
4.6. Notation: Command
4.7. Notation: People
4.8. Notation: External System
4.9. Notation: Policy
4.10. Notation: Read Model
4.11. Notation: Sketch
4.12. Notation: Hot Spot
4.13. Notation: Value (created and destroyed)
4.14. The picture that explains everything
Self-assessment quizz
Feedback: satisfaction survey
5.1. Introduction
5.2. Notation: Domain Event and Command
5.3. Notation: Read Model
5.4. Notation: Policy
5.5. Notation: Policy. Manual or Automatic
5.6. Notation: Policy. Evolutionary changes
5.7. Notation: Policy. Listener
5.8. Notation: Policy. Process Manager
5.9. Notation: Policy. Saga
5.10. Notation: Policy. Saga. Extended scope
5.11. Notation: Policy. Saga. Design
5.12. Notation: Policy. Saga. Orchestration
5.13. Notation: Policy. Saga. Orchestration in messaging
5.14. Notation: Policy. Saga. Choreography
5.15. Notation: Policy. Saga. Choreography in messaging
5.16. Notation: Policy. Saga. Mixing orchestration and choreography
5.17. Notation: Policy. Saga. Messaging
5.18. Notation: Policy. Saga. Identification tips
5.19. Notation: Policy. Saga. Trigger patterns
5.20. Notation: Policy. Saga. Robust example
5.21. Notation: Policy. Process Managers vs Saga
5.22. Notation: Policy. Ecosystem of tools for Sagas and Process Managers
5.23. Notation. Aggregate
5.24. Notation. Aggregate. Rules of thumb
5.25. Notation. Aggregate. Finding the right size
5.26. Notation. Aggregate. Life cycle
5.27. Notation. Aggregate. State transitions
5.28. Notation. Aggregate. From timeline view to responsibility view
5.29. Notation. Aggregate. Example
5.30. Example Mapping. Rules. Aggregates and Policies
5.31. Example Mapping. Notation
5.32. Example Mapping. Notation: User Story
5.33. Example Mapping. Notation: Rule
5.34. Example Mapping. Notation: Example
5.35. Example Mapping. Notation: Question
5.36. Example Mapping. Notation: Robust example
5.37. The picture that explains everything (with the Aggregate)
5.38. Implementation friendly to CQRS and Event Sourcing
5.39. Symmetries
5.40. Shake the system
5.41. Shake the system. Domain-Driven Design chief heuristic
5.42. Shake the system. Raise the bar
5.43. Shake the system. Play with conversational terms
5.44. Shake the system. Model Exploration Whirlpool
Self-assessment quizz
Feedback: satisfaction survey
You can start learning EventStorming now! The next course presentation is on Tuesday, March 28, 2023 at 18:00 (UTC+2). Sign up through Worldwide EventStorming Meetup.
“At my workplace, we are starting to adopt Domain-Driven Design. With this course, I have been able to identify the interrelation between EventStorming and Domain-Driven Design, in addition to acquiring a very solid foundation in EventStorming. There is no doubt that I am prepared to carry out EventStorming workshops with my coworkers and get the most out of them. It is one more step toward establishing the philosophy of Domain-Driven Design in our business culture.”
“Daniel has done an outstanding job creating the first asynchronous online EventStorming course. Through detailed explanations, examples, demonstrations, and self-assessment quizzes, it gathers everything you need to fully comprehend EventStorming. I feel satisfied to have invested resources and the necessary time in this course.”
“I was curious to understand what is done with so many different coloured sticky notes during an EventStorming workshop. Most importantly, how it integrates with software development. Certainly, the course has solved these doubts.”
“From the course, I highlight how EventStorming brings to light the strategic and tactical design patterns of Domain-Driven Design.”
“When I started reading about EventStorming I saw that it had a lot of potential, and I got excited about being a facilitator. In this sense, the course has been a perfect guide for future facilitators and exposes, in an easy way, the dynamics of the EventStorming workshops.”
“With this course, I learned how to use the EventStorming technique. I feel able to apply it to reduce the misunderstanding and mismatch that often occurs between the people who know about the business and the technical ones who develop the software to support it.”
“What I liked best about Big Picture EventStorming was learning the heuristics to discover Subdomains and Bounded Contexts. In the Software Design EventStorming, it was interesting the explanations about Aggregates and Policies (Listeners, Process Managers and Sagas), and how they are linked with Example Mapping.”
“I was looking for an EventStorming course that I could do at my own pace, online and asynchronously. In addition, I can expose my doubts in each lesson. It is not simply a course in which there is no possibility of communicating with the instructor. Daniel performs a tutoring by answering the questions, unresolved doubts or commenting on the comments.”
“I wanted to learn about EventStorming and this course was recommended to me. It has been brilliant and has met my expectations. It covers everything a beginner in EventStorming should know and delves deeper into the topics. I also liked the ease of use of the virtual learning platform, which is intuitive.”
“Coming from an Agile background, I discovered EventStorming to be a useful and practical tool to add to my toolbox. For this reason, I decided to enroll in the course. In addition, it is very complete, the learning objectives and the contents are very well specified, and it is the only EventStorming course that I found with this training modality.”