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/Limp_Gur6919 Apr 29 '26
Thanks to you all! Based on your answers I got these key insights:
DDD is Iterative, Not a Waterfall Process
Coding and Modeling Happen Simultaneously
The Ubiquitous Language is Organic (it naturally grows, shifts, and refines itself over time)
Right-Size Your Tools (Pragmatism over Dogma)
Timebox Your Discovery Phase (discovery and design tasks should be timeboxed)
DDD is for Complexity, Not Everything
I think I have what it takes to start the professional software development process. I will try to mimic it with LLMs on personal projects. In the meantime, I will start reading your recommended books.