Domain-Driven Design

Evans, E. (2003). Domain-Driven Design: Tackling Complexity in the Heart of Software. Addison-Wesley.

Type

Book

Intellectual base

Textbook

Year

2003

Link

https://www.informit.com/store/domain-driven-design-tackling-complexity-in-the-heart-9780321125217

Cited from

architecture_urban_planning, philosophy

Cited by

4 citations across 4 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Boundary
  • Evans's Domain-Driven Design

    This sourcebounded contexts — explicit boundaries around domain models within which a uniform ubiquitous language applies, with explicit integration rules at the boundary.

• Design Patterns

  • This sourcePattern-language treatment of domain modeling (Entity, Value Object, Aggregate, Repository, Bounded Context, Ubiquitous Language). Cited inline in §3 and §5 (tier B — supports the DDD-patterns generalization claim).

Mechanisms

• Adapter or Translation Shim
  • Its central failure is that the "temporary" shim becomes permanent load-bearing infrastructure — because everything works, no one migrates, and the shim silently hardens into part of the contract, the very drift the archetype warns against.

    This sourceIts whole value is being a boundary you own; its whole risk is forgetting it was meant to be temporary.

• Domain Model
  • Following the domain-driven design practice of building a shared model in a ubiquitous language,

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Registry ID ref:0395203ed21c · see in the full table