Domain Driven Design

by wondelaic172996495beMIT2.3K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", "strategic design", "the code doesnt match the business", or "how do we split this big system". Also trigger when breaking a monolith into services, defining service boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.

Instructions onlySoftware Development
  1. c172996495beCurrentcommit c172996Published Oct 8, 2026

Source and attribution

Source:wondelai/skillsindomain-driven-designat commitc172996

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal