38'13" on [[rt-792-ru]] | [web](https://radio-t.com/p/2022/02/05/podcast-792/) | [mp3](https://cdn.radio-t.com/rt_podcast792.mp3) (2022-02-05)
# DDD on Radio-T 792
(38'13") [[Vlad Khononov]] the author of [[Learning Domain-Driven Designđź“š2021|Learning Domain-Driven Designđź“š (2021, O'Reilly)]] appears in the show.
### [[Learning Domain-Driven Designđź“š2021|Learning DDDđź“š]]
**(51'00") Vlad the Guest:**
There are three main books on [[Domain Driven Design|DDD]]:
- [[Domain Driven Designđź“š2004|Evansđź“š]] (the blue one)
- [[Implementing Domain Driven Designđź“š2013|Vaughn Vernonđź“š]] (the red one)
- and later he (Vernon) wrote another one — very short and concise [[Domain-Driven Design Distilled📚2016|DDD Distilled📚]]
In my experience, people find both Vernon's and Evans’s books hard to read.
**Umputun:**
Honestly, your book isn’t the easiest read either. And your YouTube lectures put me to sleep after 15 minutes — all your books are kind of heavy.
**Alexey:**
Well, it’s not an easy topic, Umputun. This isn’t just slapping together microservices — you actually have to think.
### DDD Distilled
**Alexey:**
But actually, [[Domain-Driven Design Distilled📚2016|DDD Distilled📚]] is a pretty easy read, I think. Props to Vaughn for that — I feel like it does a good job of getting the core idea across. I never made it through the original _Domain-Driven Design_ book — it’s just really tough to get through. But then again, it’s hard because it’s _super_ abstract. Like, all the advice is basically “let’s do things the right way and not the wrong way” — that’s Evans for you.
**Vlad the Guest:**
The problem with [[Domain-Driven Design Distilled📚2016|Distilled📚]] is that it’s a little _too_ distilled — no code, no examples, and that makes it hard for developers to actually apply it. I wanted to write a book that’s shorter than the red and blue ones, but takes someone from a “white belt” to a “brown belt.” If you want to become a “black belt,” go read the red and blue books.
### The limits of DDD applicability
**(57'51") Vlad the Guest on the boundaries of applicability:**
Back in 2004, the idea was that you had developers, and then you had domain experts you’d talk to in order to understand the business domain. But nowadays, in a lot of software companies, the developers _are_ the domain experts — and that creates a mismatch. ([[Domain Driven Design|DDD]])