Understanding Core, Generic, and Supporting Domains in DDD Using a Peach Tree Analogy

The author, a senior architect, revisits the peach‑tree example previously used to illustrate Domain‑Driven Design (DDD) and shows how to map a business problem onto domains and subdomains.

Step 1: Identify the research object – the peach tree – as the overall domain to be studied.

Step 2: Split the domain into organs (roots, stem, leaves, flowers, fruits, seeds), which become subdomains; these are further grouped into nutritional organs (roots, stem, leaves) and reproductive organs (flowers, fruits, seeds).

Step 3: Within each subdomain, distinguish core, generic, and supporting domains, then break them down into organizations (protective, nutritional, transport) and finally into cells (e.g., root‑hair cells, vessel cells).

The article defines key terms: Domain – a business area; Subdomain – a finer‑grained part of a domain; Core Domain – the most critical part that provides competitive advantage; Generic Domain – reusable functions such as authentication; Supporting Domain – non‑core, non‑generic functions that enable operations.

It explains why this classification matters: the core domain drives profit and should receive the most resources, the generic domain offers common services that can be bought or reused, and the supporting domain handles ancillary tasks; aligning resources accordingly improves efficiency and strategic focus.

Overall, dividing a system into core, generic, and supporting domains helps teams allocate effort, clarify responsibilities, and design microservices that reflect business priorities.