Course structure and contents

    1. 1.1. Index

    2. 1.2. The origin of EventStorming

      FREE PREVIEW
    3. 1.3. Introduction to Domain-Driven Design

    4. 1.4. Some essential Domain-Driven Design concepts

    5. 1.5. Difference between domain and business

    6. 1.6. The journey of EventStorming (past and present)

    7. 1.7. EventStorming books

    8. 1.8. EventStorming popularity

    9. 1.9. Who is using EventStorming?

    10. 1.10. What is EventStorming?

    11. 1.11. Why EventStorming?

    12. 1.12. For who is EventStorming?

    13. Self-assessment quizz

    14. Feedback: satisfaction survey

    1. EventStorming fields of application

    2. Self-assessment quizz

    3. Feedback: satisfaction survey

    1. 3.1. Index

    2. 3.2. Scope

    3. 3.3. The key ingredients

    4. 3.4. The importance of the facilitator

      FREE PREVIEW
    5. 3.5. Invitations phase

    6. 3.6. Room setup phase

    7. 3.7. Kick-off phase

    8. 3.8. Chaotic exploration phase

    9. 3.9. Enforcing the timeline phase

    10. 3.10. People and Systems phase

    11. 3.11. Explicit walk-through phase

    12. 3.12. Reverse narrative phase

    13. 3.13. Value created and destroyed phase

    14. 3.14. Problems and Opportunities phase

    15. 3.15. Pick the right problem phase

    16. 3.16. Discover Subdomains and Bounded Contexts phase

    17. 3.17. Wrapping up phase

    18. Self-assessment quizz

    19. Feedback: satisfaction survey

    1. 4.1. Introduction

    2. 4.2. Opening strategies

    3. 4.3. Midpoint strategies

    4. 4.4. Notation

    5. 4.5. Notation: Domain Event

    6. 4.6. Notation: Command

    7. 4.7. Notation: People

    8. 4.8. Notation: External System

    9. 4.9. Notation: Policy

    10. 4.10. Notation: Read Model

    11. 4.11. Notation: Sketch

    12. 4.12. Notation: Hot Spot

    13. 4.13. Notation: Value (created and destroyed)

    14. 4.14. The picture that explains everything

    15. Self-assessment quizz

    16. Feedback: satisfaction survey

    1. 5.1. Introduction

    2. 5.2. Notation: Domain Event and Command

    3. 5.3. Notation: Read Model

    4. 5.4. Notation: Policy

    5. 5.5. Notation: Policy. Manual or Automatic

    6. 5.6. Notation: Policy. Evolutionary changes

    7. 5.7. Notation: Policy. Listener

    8. 5.8. Notation: Policy. Process Manager

    9. 5.9. Notation: Policy. Saga

    10. 5.10. Notation: Policy. Saga. Extended scope

    11. 5.11. Notation: Policy. Saga. Design

    12. 5.12. Notation: Policy. Saga. Orchestration

    13. 5.13. Notation: Policy. Saga. Orchestration in messaging

    14. 5.14. Notation: Policy. Saga. Choreography

    15. 5.15. Notation: Policy. Saga. Choreography in messaging

    16. 5.16. Notation: Policy. Saga. Mixing orchestration and choreography

    17. 5.17. Notation: Policy. Saga. Messaging

    18. 5.18. Notation: Policy. Saga. Identification tips

    19. 5.19. Notation: Policy. Saga. Trigger patterns

    20. 5.20. Notation: Policy. Saga. Robust example

    21. 5.21. Notation: Policy. Process Managers vs Saga

    22. 5.22. Notation: Policy. Ecosystem of tools for Sagas and Process Managers

    23. 5.23. Notation. Aggregate

    24. 5.24. Notation. Aggregate. Rules of thumb

    25. 5.25. Notation. Aggregate. Finding the right size

    26. 5.26. Notation. Aggregate. Life cycle

    27. 5.27. Notation. Aggregate. State transitions

    28. 5.28. Notation. Aggregate. From timeline view to responsibility view

    29. 5.29. Notation. Aggregate. Example

    30. 5.30. Example Mapping. Rules. Aggregates and Policies

    31. 5.31. Example Mapping. Notation

    32. 5.32. Example Mapping. Notation: User Story

    33. 5.33. Example Mapping. Notation: Rule

    34. 5.34. Example Mapping. Notation: Example

    35. 5.35. Example Mapping. Notation: Question

    36. 5.36. Example Mapping. Notation: Robust example

    37. 5.37. The picture that explains everything (with the Aggregate)

    38. 5.38. Implementation friendly to CQRS and Event Sourcing

    39. 5.39. Symmetries

    40. 5.40. Shake the system

    41. 5.41. Shake the system. Domain-Driven Design chief heuristic

    42. 5.42. Shake the system. Raise the bar

    43. 5.43. Shake the system. Play with conversational terms

    44. 5.44. Shake the system. Model Exploration Whirlpool

    45. Self-assessment quizz

    46. Feedback: satisfaction survey

Course details

  • €240,00 / month
  • 107 lessons
  • 7.5 hours of video content
  • English
  • Videos with captions
  • Certificate of completion

Instructor

Daniel Solé Morera

EventStorming facilitator and instructor | Domain-Driven Designer | Software engineer

About me: https://www.dsolemorera.com/about-me

Want to know more?

Video summary of the training programme

Training programme

Next presentation

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.

  • 00 Days
  • 00 Hours
  • 00 Minutes
  • 00 Seconds

Course opinions

“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.”

Arthur M.

“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.”

Emma W.

“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.”

Eric R.

“From the course, I highlight how EventStorming brings to light the strategic and tactical design patterns of Domain-Driven Design.”

Camila B.

“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.”

Uwe B.

“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.”

Emilia S.

“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.”

Ambrus H.

“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.”

Pedro E.

“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.”

Aurora M.

“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.”

Selena L.