Domain Driven Design - So Your Code Speaks Plain Language
summary
The talk explains how Domain-Driven Design (DDD) reduces errors when translating complex business specifications into Java code by establishing a ubiquitous language and clear boundaries between domain and technical layers. It covers concrete DDD practices used in a large multi-thousand-day project: domain classes with only business data, separation of technical concerns, and explicit structures for services and repositories to improve code clarity and maintainability.
AI-written summary · about
chapters (11)
- 0:00Domain Driven Design introduction
- 3:53Problems in classic software
- 7:44Information loss in projects
- 11:17Shared language with DDD
- 15:06Concretizing requirements
- 19:23Language challenges in code
- 23:16Separating business and technical layers
- 28:56Defining domain objects and services
- 33:11Using processes and diagrams
- 36:18DDD effort and benefits
- 40:14Conclusion and experiences
related talks
46mDomain Driven Design The Basics
45mDomain Driven Modular Architecture
38mWhat I talk about when I talk about Domain Driven design
48mDomain-Driven Design tactically and practically
49mHow to cook Domain Driven Design
35mTrivialization of DDD or Not?
59mDomain-Driven Design - Where Rubber Meets the Road
55mDomain-Driven Design: back to the roots