In 2024, the software industry fell in love with Microservices, but many failed because they ignored Chapter 18 of Evans’ book.
: Diagrams that document the relationships and data flows between different Bounded Contexts. Tactical Design: The Building Blocks
: While page 18 shows the "stumbling" start, it sets the stage for creating a Ubiquitous Language —a shared vocabulary that bridges the gap between developers and stakeholders. domain driven design eric evans epub 18
Given the book's length and depth, new learners might misunderstand which part is most critical. A search for "Chapter 18" suggests a desire to skip to the advanced material. While the book is best appreciated as a cohesive whole, later sections focus on the principles of "Strategic Design," such as:
DDD mandates that the team defines a single, shared language used by business stakeholders and developers alike. This language is embedded directly into the source code. If a business expert calls a customer profile an "Account," the code must use the class name Account , not User or Client Profile . 2. Bounded Contexts In 2024, the software industry fell in love
One context depends on another; the upstream team must deliver what the downstream team needs.
Once you have defined your Bounded Contexts, you must map how they interact. Evans outlines several relationship patterns in his book: Given the book's length and depth, new learners
As a system grows, it becomes harder to maintain. Evans emphasizes the concept of —separating your system into three distinct subdomains:
: In Evans' supplemental presentations (like "What I've Learned Since the Book"), page 18 details a four-step process for Context Mapping .
, often called the "Blue Book," is a foundational text in software engineering. Published in 2003, it shifted the focus of development from technical frameworks to the "domain"—the specific business problem the software is meant to solve. Core Philosophy