Core domain (subdomains)
The part of the business that sets it apart from competitors; supporting and generic subdomains are the rest, which can stay simple or be bought.
DDD splits the business into subdomains of three kinds. The core domain is why customers pick you: for a booking marketplace that may be matching patients with the right doctor and slot. Supporting subdomains are specific to you but not a differentiator, such as an internal admin panel. Generic subdomains are the same everywhere: payments, email, login.
The split decides where to spend senior time. The core gets the best people, careful modeling and its own bounded context; supporting areas can be plain CRUD; generic ones are usually a build vs buy decision that ends with buy. The DDD Crew core domain charts place each subdomain by business differentiation and model complexity.
Sources
- GitHub: ddd-crew/core-domain-charts github.com
Related terms
- DDD (domain-driven design): Designing software around the business’s own language and rules, with the code split where that language changes meaning.
- Build vs buy: The choice between paying for a ready-made product and building your own software, including what each costs over time.
- Bounded context: A part of a system where each business term has one meaning and one model, with explicit translation at its edges.
- Context map (DDD): A diagram of the bounded contexts in a system and the kind of relationship between each pair: who depends on whom and how models are translated.
