Learning Domain-Driven Design — Conversation with Vlad Khononov

The finale features author Vlad Khononov. He wanted to make Eric Evans's ideas more accessible and add event sourcing, CQRS, and Data Mesh. The discussion traces the O'Reilly report into a book, addresses a Russian translation, and stresses the boundaries of Ubiquitous Language.

DDD rarely arrives through a company-wide decree; teams reach its principles through questions and constraints. Vlad recommends broad startup boundaries instead of premature microservices. WolfDesk is intended as an executable example, but the book teaches reasoning rather than copy-ready code.

Reference data may be a value object or entity depending on change. Vlad models in Miro and treats code generation as a prompt to inspect complexity. A database view is valid as a published contract. A saga coordinates services, a process manager owns a lifecycle, and anti-corruption layer placement depends on context.

A strict transaction across two databases can expose a wrong aggregate boundary, so the required consistency level comes first. Vlad introduces Balancing Coupling in Software Design and closes with the distinction: Ubiquitous Language within a bounded context is core DDD; aggregates, value objects, and other tactical patterns are replaceable.