As systems grow, the same word can mean different things to different teams. A customer in billing may not have the same lifecycle or data requirements as a customer in support. Bounded contexts make these differences explicit.
Find model boundaries
Look for distinct vocabularies, ownership, business rules, and rates of change. A context should own a coherent model and the decisions made with it. Do not split contexts merely because two database tables are large.
Define context contracts
Contexts communicate through explicit APIs, events, or carefully designed shared interfaces. Avoid reaching into another context's tables to make a decision because that bypasses the owning model's rules.
A translation layer can map one context's terminology into another's. This prevents one team's internal model from becoming a universal schema.
Choose deployment boundaries later
A bounded context does not have to be a separate microservice. It can be a module inside a monolith with clear ownership and dependencies. Separate deployment adds network, operations, and consistency costs.
Checklist
- Identify distinct business vocabularies.
- Assign ownership of rules and data.
- Define explicit integration contracts.
- Translate between context-specific models.
- Keep deployment topology independent from domain boundaries.