- Популярные видео
- Авто
- Видео-блоги
- ДТП, аварии
- Для маленьких
- Еда, напитки
- Животные
- Закон и право
- Знаменитости
- Игры
- Искусство
- Комедии
- Красота, мода
- Кулинария, рецепты
- Люди
- Мото
- Музыка
- Мультфильмы
- Наука, технологии
- Новости
- Образование
- Политика
- Праздники
- Приколы
- Природа
- Происшествия
- Путешествия
- Развлечения
- Ржач
- Семья
- Сериалы
- Спорт
- Стиль жизни
- ТВ передачи
- Танцы
- Технологии
- Товары
- Ужасы
- Фильмы
- Шоу-бизнес
- Юмор
Why AI is the Third Coming of Domain-Driven Design
subscribe to the newsletter: https://deararchitects.xyz
Balancing Coupling in Software Design: https://amzn.to/4rotZlz
Learning Domain-Driven Design: https://amzn.to/4tGQvb2
Most architects have been thinking about coupling the wrong way for years. Not as something to understand and design deliberately but as something to eliminate. That misunderstanding is behind most of the distributed monolith disasters of the microservices era.
In this episode, Vlad, author of Balancing Coupling in Software Design, shares what he learned after building a textbook distributed monolith while following best practices to the letter. We dig into why coupling is unavoidable, what the three dimensions of coupling actually are, and why strategic DDD consistently beats tactical DDD for large systems.
But the conversation takes an unexpected turn: Vlad argues AI is the third coming of Domain-Driven Design. When you prompt an AI in natural language, ambiguous domain models don't just slow your team down — they get baked silently into generated code. The same discipline that makes systems evolvable turns out to be the foundation for working effectively with AI.
0:00 Intro & guest welcome
1:00 Why modeling is the foundation of good software design
2:45 Rethinking coupling — it's not what you think
8:00 How microservices created the distributed monolith trap
14:00 The real cost of splitting without fixing the design
19:00 Why pain is your best architectural signal
23:00 Domain-Driven Design has a reputation problem
28:00 Strategic DDD vs tactical DDD — what actually matters
33:00 How to approach a brownfield system
37:00 Subdomains: the hardest part of DDD nobody talks about enough
41:00 Bounded contexts and why less is more for startups
46:00 AI is the third coming of Domain-Driven Design
52:00 Teaching DDD to an LLM — what Vlad actually tried
55:00 Working code is no longer the challenge. Evolvable code is.
1:00:00 What Vlad would change in his book
1:07:00 What's next
===================================
Follow me for more tips!
My gear: https://www.amazon.co.uk/shop/my50cents?ref_=cm_sw_r_cp_ud_aipsfshop_W744H9NEJG7C9T3JMFC2
Spotify: https://open.spotify.com/show/0W5YEY5T3ApuYS8H9I3DzL?si=c279c2df086b4d8f
Twitter: https://twitter.com/lucamezzalira
LinkedIn: https://www.linkedin.com/in/lucamezzalira
Instagram: https://instagram.com/mezzalab
Видео Why AI is the Third Coming of Domain-Driven Design канала My 50 cents
Balancing Coupling in Software Design: https://amzn.to/4rotZlz
Learning Domain-Driven Design: https://amzn.to/4tGQvb2
Most architects have been thinking about coupling the wrong way for years. Not as something to understand and design deliberately but as something to eliminate. That misunderstanding is behind most of the distributed monolith disasters of the microservices era.
In this episode, Vlad, author of Balancing Coupling in Software Design, shares what he learned after building a textbook distributed monolith while following best practices to the letter. We dig into why coupling is unavoidable, what the three dimensions of coupling actually are, and why strategic DDD consistently beats tactical DDD for large systems.
But the conversation takes an unexpected turn: Vlad argues AI is the third coming of Domain-Driven Design. When you prompt an AI in natural language, ambiguous domain models don't just slow your team down — they get baked silently into generated code. The same discipline that makes systems evolvable turns out to be the foundation for working effectively with AI.
0:00 Intro & guest welcome
1:00 Why modeling is the foundation of good software design
2:45 Rethinking coupling — it's not what you think
8:00 How microservices created the distributed monolith trap
14:00 The real cost of splitting without fixing the design
19:00 Why pain is your best architectural signal
23:00 Domain-Driven Design has a reputation problem
28:00 Strategic DDD vs tactical DDD — what actually matters
33:00 How to approach a brownfield system
37:00 Subdomains: the hardest part of DDD nobody talks about enough
41:00 Bounded contexts and why less is more for startups
46:00 AI is the third coming of Domain-Driven Design
52:00 Teaching DDD to an LLM — what Vlad actually tried
55:00 Working code is no longer the challenge. Evolvable code is.
1:00:00 What Vlad would change in his book
1:07:00 What's next
===================================
Follow me for more tips!
My gear: https://www.amazon.co.uk/shop/my50cents?ref_=cm_sw_r_cp_ud_aipsfshop_W744H9NEJG7C9T3JMFC2
Spotify: https://open.spotify.com/show/0W5YEY5T3ApuYS8H9I3DzL?si=c279c2df086b4d8f
Twitter: https://twitter.com/lucamezzalira
LinkedIn: https://www.linkedin.com/in/lucamezzalira
Instagram: https://instagram.com/mezzalab
Видео Why AI is the Third Coming of Domain-Driven Design канала My 50 cents
software architecture domain driven design DDD microservices distributed systems coupling cohesion bounded contexts ubiquitous language balancing coupling in software design software design modular software distributed monolith event storming subdomains strategic DDD tactical DDD AI software development software engineering clean architecture system design software architecture podcast dear architects software design principles evolutionary architecture AI
Комментарии отсутствуют
Информация о видео
3 марта 2026 г. 18:07:31
01:02:33
Другие видео канала




















