Bounded Context Block
A bounded context defines where a model, language, ownership, and generation boundary apply.
When To Use It
Use a Bounded Context block when the canvas covers more than one business capability, team, deployment unit, or vocabulary. Bounded contexts prevent a large model from pretending that every term has one meaning everywhere.
Required Data
- Name: capability name, such as Billing, Fulfilment, or Claims Assessment.
- Purpose: business outcome the context owns.
- Owned language: key terms and their meaning inside this context.
- Owned blocks: aggregates, commands, events, policies, and read models inside the boundary.
- Interfaces: integration events, APIs, or files used to communicate with other contexts.
Recommended Data
- Team owner: team accountable for the context.
- Generation target: module, service, application, or package.
- Persistence style: current-state, event-sourced, or mixed.
- Deployment preference: same application, separate service, or hosted boundary on SAAScade Cloud.
- Context relationships: upstream, downstream, customer-supplier, shared kernel, or anti-corruption layer.
Examples
- Commerce: Catalog, Checkout, Payments, Fulfilment, Returns.
- Insurance: Policy Administration, Claims Intake, Claims Assessment, Payments, Fraud Review.
- SaaS: Identity, Subscription Billing, Entitlements, Usage Metering, Support.