EventStorming, from the big picture to code
- eventstorming
- ddd
- facilitation
Five short videos on the three levels of EventStorming and the notation that ties them together.
· 4 min read
Service
Domain-Driven Design & EventStorming
Explore the business with the people who know it, and turn what you learn into clear boundaries, models and event-driven architectures.
At a glance
- Format
- Workshops, design coaching, architecture
- Duration
- From a single workshop to several months
- Where
- Remote, on site in Luxembourg and the EU when it matters
- Languages
- English, French
When it helps
Sounds familiar?
- Business and IT describe the same process in different words, and requirements get lost in translation.
- You are splitting a monolith into services and do not know where to draw the boundaries.
- A new project starts, and nobody has the full picture of the domain yet.
- Your coding agents invent names and business rules, because your domain knowledge is not written anywhere they can read.
What I do
What I take on
EventStorming workshops
Big Picture, process modelling and software design, with business and tech at the same wall.
Bounded contexts
Where to draw the boundaries between models, teams and systems, and how they relate.
Domain modelling
Aggregates, invariants and a shared language that shows up in the code.
CQRS and event sourcing
Architectures that keep the history of what happened, when the domain calls for it.
Domain-Driven Design with AI
Agents mine legacy code and documents to prepare the exploration. The language and boundaries you agree on are then written where coding agents can use them.
Team coaching
Helping developers apply Domain-Driven Design in their own code, through pairing, katas and reviews.
Ecosystem
Methods and community
I have practised Domain-Driven Design since 2008, and learned much of it from the people who shaped it.
Methods I use
- EventStorming From the big picture to code
- Context mapping Relations between contexts
- Specification by example Rules agreed with examples
- CQRS Separate reads and writes
- Event sourcing State as a history of events
- Knowledge graph The domain, queryable by agents
Where I learned and shared
- Greg Young CQRS & DDD workshops · 2013, 2014
- DDD Exchange Skills Matter · 2014, 2015
- KanDDDinsky Speaker · 2017
- EventStorming Summit Avanscoperta · 2018
- Domain Modeling Made Functional Avanscoperta · 2020
EventStorming was created by Alberto Brandolini. His site has the book and the reference material.
Formats
Ways to work together
Workshop
A day or two
A Big Picture EventStorming that puts the whole domain on one wall, with a written summary of hotspots and next steps.
Design coaching
Part-time, over months
Regular sessions with your team, from process modelling down to the code.
Architecture
Several months
Boundaries, target architecture and the first services, designed and built with your team.
- 2019 – 2021
Agile coach & architect · TadaWeb
Technical coaching on EventStorming, Domain-Driven Design, CQRS and event sourcing, alongside agile coaching and training.
- 2019
Agile coach & architect · Banque Internationale à Luxembourg, Foyer
Domain-Driven Design, CQRS and event sourcing consulting, EventStorming workshops, and a technical community of practice at Foyer.
- 2013 – 2015
Agile coach & architect · POST Luxembourg
CQRS and event sourcing at the core of the mobile app postal agents use on their rounds, then the routing module of a new order management system, built by several Scrum teams in parallel.
Blog
Related writing
Other ways I can help
Contact
Let's build something good together.
Tell me about your context and timeline. I usually reply within one business day.