Learning Domain-Driven Design — Chapter 1
Episode participants
The complete participant roster has not yet been confirmed by the available sources.
What we discussed on the recording
The first episode opens Vlad Khononov's Learning Domain-Driven Design and its strategic-design section. The discussion starts with business logic: code, patterns, and infrastructure solve a business problem, while the most valuable logic captures how a company differs from its competitors.
The domain is divided into core, supporting, and generic subdomains. A bakery and internal products show the difference between competitive advantage, necessary custom support, and a hard problem already solved by the market. Categories can change: a supporting capability may become a core product and a generic solution for others.
Ubiquitous Language prevents a telephone game among experts, analysts, and developers. It uses business terms without implementation details and keeps semantics consistent in conversation and code. Yet it is unified only within a bounded context: the same application means different things at different process stages.
A context map connects models and teams. The hosts examine partnership, shared kernel, upstream and downstream, conformist, anti-corruption layer, open-host service, and published language. Each pattern reflects a balance of influence and protects the core domain; sometimes duplicating a small rule is cheaper than adding an unnecessary integration.