← experimental
Contents
  1. Background
  2. Core Positions
  3. Books

Books in this wiki: Learning Domain Driven Design

Background

Vlad (Vladik) Khononov is a software engineer with over 20 years of industry experience, working for companies of various sizes in roles ranging from webmaster to chief architect. He lives in Northern Israel. He maintains an active media career as a public speaker, blogger, and author, and travels internationally consulting on domain-driven design, microservices, and software architecture.

His first exposure to DDD came through Evans's Blue Book, which he found initially impenetrable (partly due to English being his third language). After several years of practice, DDD became a career-defining framework for him. He has spent over 10 years teaching DDD in-person and online, which informed both the book's structure and its emphasis on accessibility.

Core Positions

  • Software project failure is fundamentally a communication problem; DDD is the systematic solution.
  • The subdomain type (core / generic / supporting) is the primary driver of implementation strategy — what tools to use, who to assign, whether to outsource.
  • Ubiquitous language is not a glossary; it is a living model co-developed with domain experts and embedded in code.
  • Tactical pattern choice (transaction script → active record → domain model → event-sourced domain model) must be driven by the complexity of the business logic, not developer preference.
  • DDD is not just for large systems or complex domains — the strategic tools add value even in simpler contexts by aligning software design with business intent.

Books

Learning Domain Driven DesignLearning Domain-Driven Design (2022)

An accessible, complete introduction to DDD as a methodology — strategic design (domain analysis, bounded contexts, integration patterns) through tactical design (business logic implementation patterns), then DDD in practice (EventStorming, brownfield, evolution) and DDD relationships to microservices, EDA, and data mesh. The most thorough DDD source in this wiki. Evolved from an O'Reilly report titled "What Is Domain-Driven Design?" (2019).