Boundary Context and Subdomain

Boundary Context refers to the boundaries of a business context. Within this boundary, when we discuss a specific business concept, there will be no ambiguity or confusion in understanding or cognition. The Boundary Context is a key guarantee for the unification of language. In future technical implementations, business requirements from different boundary contexts that are conceptually similar should be developed and maintained by separate teams as much as possible.

Subdomain refers to the clarification and division of the problem domain, and it also serves as an important reference for prioritizing resource allocation. The types of subdomains include:

  1. Core Domain: This is the core differentiator and competitive advantage of the current product, and the foundation and profit source for the entire business. Without the core domain, the business cannot operate. The core domain requires the most favorable resources (including the best-skilled personnel) and careful, high-quality design.
  2. Supporting Subdomain: These domains address issues that support the operation of the core domain. While not as critical as the core domain, they have strong and unique requirements that cannot be easily met with off-the-shelf solutions. Custom development by a specialized team is necessary.
  3. Generic Subdomain: These domains solve common problems that are frequently encountered within the industry, and are likely to have existing solutions. These solutions can be used by purchasing or with minimal customization.

image.png

Domain Name Domain Type Bounded Context Domain Term
Borrowing Domain core Book Context Book,Fine
Borrowing Domain core Record Context Borrowing Record,Reservation Record
Account Domain supporting Account Context Account
Notification Domain Generic Notification Context Welcome Notification,Lost Notification,Overdue Notification

Based on business boundaries, three domains have been identified: Borrowing Domain, Account Domain, and Notification Domain. These domains correspond to different contexts:


This structure allows for clear distinctions in responsibilities and resource allocation within different business contexts, helping ensure that teams focus on the most important and relevant domains for their expertise.