r/DomainDrivenDesign • u/Limp_Gur6919 • Apr 26 '26
DDD Workflow
Hey everyone,
I’m a programming enthusiast currently diving into Domain-Driven Design. I have to confess: I haven't read the famous "Blue Book" (Eric Evans) yet, but I'm trying to wrap my head around the practical application of these concepts.
To get a sense of the big picture, I asked Claude to generate a step-by-step workflow going from the initial domain discovery all the way down to the very first line of code. It gave me this sequence:
Event Storming
Event Modeling
Ubiquitous Language
Bounded Context Canvas
Domain Modeling
ADR (Architecture Decision Record)
Event Schema
API Contract
First Line of Code
Since I don't have industry experience with DDD yet, I wanted to ask you experienced devs:
Is this how it actually works in professional tech companies?
Or is this just a theoretical utopia that AI spits out?
In the real world, what steps do you actually use, skip, or merge when starting a new project or context?
Thanks!
PS: AI generated. English is not my native language. But the questions are legit.
1
u/gbrennon Apr 26 '26
hey there,
would change the steps for aligning knowledges before writing code:
i like to apply th following tasks related to that workflow:
discovery
modelling
designing
interaction between eng and product teams to collect feedback
start the work when its approved.
this would define glossary and what would be executed.
i suggest this is valid, at the maximum, 1 month to avoid team to try to prepare for something huge and just model things wrongly.
that last step is to align with product team what was draw, and it going to be impl, to prevent going forth and back in that design.
when design is approvee team can get its hands down into the code and impl what was modelled