book

Domain-Driven Design Distilled, 1/e

by Vaughn Vernon

May 2016

Intermediate to advanced

176 pages

3h 36m

English

Addison-Wesley Professional

Read now

Unlock full access

Who Is This Book For?What This Book CoversConventions
Will DDD Hurt?Good, Bad, and Effective DesignStrategic DesignTactical DesignThe Learning Process and Refining KnowledgeLet’s Get Started!
Domain Experts and Business DriversCase StudyFundamental Strategic Design NeededChallenge and UnifyDeveloping a Ubiquitous LanguagePutting Scenarios to WorkWhat about the Long Haul?ArchitectureSummary

What Is a Subdomain?Types of SubdomainsDealing with ComplexitySummary
Kinds of MappingsPartnershipShared KernelCustomer-SupplierConformistAnticorruption LayerOpen Host ServicePublished LanguageSeparate WaysBig Ball of MudMaking Good Use of Context MappingRPC with SOAPRESTful HTTPMessagingAn Example in Context MappingSummary
Why UsedAggregate Rules of ThumbRule 1: Protect Business Invariants inside Aggregate BoundariesRule 2: Design Small AggregatesRule 3: Reference Other Aggregates by Identity OnlyRule 4: Update Other Aggregates Using Eventual ConsistencyModeling AggregatesChoose Your Abstractions CarefullyRight-Sizing AggregatesTestable UnitsSummary
Designing, Implementing, and Using Domain EventsEvent SourcingSummary
Event StormingOther ToolsManaging DDD on an Agile ProjectFirst Things FirstUse SWOT AnalysisModeling Spikes and Modeling DebtIdentifying Tasks and Estimating EffortTimeboxed ModelingHow to ImplementInteracting with Domain ExpertsSummary

Content preview from Domain-Driven Design Distilled, 1/e

Chapter 3. Strategic Design with Subdomains

When you work on a DDD project, there are always multiple Bounded Contexts in play. One of the Bounded Contexts will be the Core Domain, and there will also be various Subdomains in other Bounded Contexts. In the previous chapter you saw the importance of dividing different models by their specific Ubiquitous Language and forming multiple Bounded Contexts. There are six Bounded Contexts and six Subdomains in the preceding diagram. Because DDD strategic design was used, the teams achieved the most optimal modeling composition: one Subdomain per Bounded Context, and one Bounded Context per Subdomain.