← Graph

The pillars of Domain Driven Design

talk 31 connections

Opening talk of wroclove.rb 2018 by Marco Heimeshoff. A language-agnostic introduction to Domain-Driven Design covering: ubiquitous language and weasel words, bounded contexts and context maps, core vs. supporting domains, Conway's law and team alignment, Cynefin-framed complexity, three-step process (extract model → semantic code → protect from corruption), EventStorming as collaborative modeling, hexagonal architecture, reasons to do DDD (risk mitigation, code-business harmony, autonomy, mastery, purpose), and risks (hierarchies, perfectionism, constraints). Includes a German shift-planning code example and a Q&A on OOP, startups, uncooperative clients, and remote modeling.

type
talk
talk The pillars of Domain Driven Design
about
Domain-Driven Design concept
Talk is an introduction to DDD and its strategic and tactical pillars.
talk The pillars of Domain Driven Design
about
Ubiquitous Language concept
Extensive section on designing a ubiquitous language free of weasel words.
talk The pillars of Domain Driven Design
about
Bounded Context concept
Talk explains bounded contexts, how to discover them, and why they are the core new idea in DDD.
talk The pillars of Domain Driven Design
about
Context Map concept
Strategic section uses context maps to place core, supporting, and generic contexts.
talk The pillars of Domain Driven Design
about
EventStorming concept
Presented as Heimeshoff's favorite collaborative modeling method.
talk The pillars of Domain Driven Design
about
Domain Storytelling concept
Listed alongside EventStorming and whirlpool as domain-discovery techniques.
talk The pillars of Domain Driven Design
about
Core Domain concept
Heimeshoff explains where to concentrate DDD effort via core-domain identification.
talk The pillars of Domain Driven Design
about
Value Object concept
Exercise refactors primitives into value types as the low-hanging fruit of DDD.
talk The pillars of Domain Driven Design
about
Anti-Corruption Layer concept
Introduced as a remedy when warehouse/shopping-cart teams are upstream/downstream.
talk The pillars of Domain Driven Design
about
Hexagonal Architecture concept
Third step: protect domain code from corruption via ports-and-adapters.
talk The pillars of Domain Driven Design
about
Weasel Words concept
Entire section on prefixes/suffixes that drain domain meaning.
talk The pillars of Domain Driven Design
about
Cynefin Framework concept
Used to decide how strongly to apply DDD per bounded context.
talk The pillars of Domain Driven Design
about
Conway's Law concept
Cited when explaining team alignment with bounded contexts.
talk The pillars of Domain Driven Design
about
DDD Whirlpool concept
Described as Eric Evans' iterative scenario/prototype modeling cycle.
talk The pillars of Domain Driven Design
about
Five Whys concept
Heuristic used during modeling to reach the real reasons.
talk The pillars of Domain Driven Design
about
CQRS concept
EventStorming stickies map directly to commands/events in a CQRS/event-sourced system.
talk The pillars of Domain Driven Design
about
Event Sourcing concept
Shown as how wall-modeling translates directly into source code.
talk The pillars of Domain Driven Design
about
Drive resource
Daniel Pink's autonomy/mastery/purpose framework used to explain DDD's developer benefits.
question Does DDD require object-oriented programming?
asked_at
The pillars of Domain Driven Design talk
First Q&A question after the talk.
question Does DDD apply to startups?
asked_at
The pillars of Domain Driven Design talk
Q&A question on startup applicability.
question How to apply DDD when the client refuses to learn ubiquitous language?
asked_at
The pillars of Domain Driven Design talk
Q&A on uncooperative clients.
question How to do DDD remotely?
asked_at
The pillars of Domain Driven Design talk
Final Q&A question on remote modeling.
person Marco Heimeshoff
authored
The pillars of Domain Driven Design talk
Delivered this talk at wroclove.rb 2018.
takeaway Eliminate Primitives With Value Types
from_talk
The pillars of Domain Driven Design talk
Explicit recommendation delivered in the talk's refactoring exercise.
takeaway One Ubiquitous Language Per Bounded Context
from_talk
The pillars of Domain Driven Design talk
Heimeshoff calls this the only new idea in Evans' DDD book.
takeaway Write Domain Code Free of Frameworks
from_talk
The pillars of Domain Driven Design talk
Third of Heimeshoff's three DDD steps.
takeaway Three Steps of DDD
from_talk
The pillars of Domain Driven Design talk
Core framing of the talk: extract, express semantically, protect.
takeaway Bounded Contexts Are Not Microservices
from_talk
The pillars of Domain Driven Design talk
Explicit warning against confusing the two.
takeaway Risks of DDD: Hierarchy, Perfectionism, Constraints
from_talk
The pillars of Domain Driven Design talk
Risks section near the end of the talk.
takeaway Standard Meetings Kill Collaboration
from_talk
The pillars of Domain Driven Design talk
Heimeshoff contrasts seated meetings with standing EventStorming.
talk The pillars of Domain Driven Design
presented_at
wroclove.rb 2018 event
Opening talk of the conference.

Provenance

Created
2026-04-17 16:17 seed
Last updated in
The Pillars of Domain Driven Design — Marco Heimeshoff at... 2026-04-17 16:18
Read by
32 extractions