book

What Is Domain-Driven Design?

October 2019

Intermediate to advanced

98 pages

1h 49m

English

Read now

Unlock full access

What Is Domain-Driven Design?Strategic DesignTactical DesignReport Structure
What Is a Business Domain?What Is a Subdomain?Types of SubdomainsWho Are Domain Experts?Conclusion
Knowledge DiscoveryCommunicationWhat Is Ubiquitous Language?Language of the BusinessExamplesConsistencyModel of the Business DomainWhat Is a Model?Effective ModelingModeling the Business DomainContinuous EffortConclusion
Example: Inconsistent ModelsWhat Is a Bounded Context?Model BoundariesScope of a Bounded ContextBounded Contexts Versus SubdomainsSubdomainsBounded ContextsThe Interplay Between Subdomains and Bounded ContextsPhysical BoundariesOwnership BoundariesConclusion
CooperationPartnershipShared KernelCustomer–SupplierConformistAnticorruption LayerOpen-Host ServiceSeparate WaysCommunication IssuesGeneric SubdomainsModel DifferencesWhen to AvoidContext MapConclusion
Transaction ScriptActive RecordDomain ModelImplementationBuilding BlocksOther Building BlocksEvent-Sourced Domain ModelEvent SourcingSource of TruthAdvantagesConclusion
Layered ArchitectureUse CasesPorts & AdaptersIntegration of Infrastructural ComponentsUse CasesCommand-Query Responsibility SegregationPolyglot ModelingImplementationProjecting Read ModelsChallengesModel SegregationUse CasesConclusion
Partnership and Shared KernelAnticorruption LayerOpen-Host ServiceDomain Events

Who Should Participate in Event Storming?What Do You Need for Event Storming?Modeling SpaceStickiesMarkersSnacksRoomThe Event Storming ProcessStep 1: Unstructured ExplorationStep 2: TimelinesStep 3: CommandsStep 4: PoliciesStep 5: External SystemsStep 6: AggregatesStep 7: Bounded ContextsConclusion
Changes in SubdomainsCore to GenericGeneric to CoreSupporting to CoreTactical Design ConcernsOrganizational ChangesDomain KnowledgeConclusion
Ubiquitous LanguageBusiness DomainContext MapBounded ContextsEvent StormingTactical PatternsValue ObjectsTransaction BoundariesEvent-Sourced Domain ModelConclusion

Part III. DDD in Practice

In this part of the report we will progress from theory to topics related to applying domain-driven design in practice:

Chapter 8 provides an introduction to “event storming,” a group modeling technique that streamlines the process of discovering domain knowledge and building a ubiquitous language.
In Chapter 9, we will look at domain-driven design from a temporal perspective and will see how to maintain and evolve both tactical and strategic designs over time.
Chapter 10 will conclude this report with a selection of tips and tricks for “gently” incorporating domain-driven design’s patterns and practices in greenfield and brownfield projects.