Identifying Bounded Contexts
You'll learn how to discover and define bounded contexts by analyzing your business domain, language patterns, and model boundaries.
A bounded context is a boundary within which a particular domain model is valid and consistent. The same word can mean different things in different parts of your organization—and that's exactly where context boundaries belong.
Understanding the Problem
In large systems, trying to maintain one unified model across the entire domain leads to confusion and compromise. A "Customer" in the sales department has different attributes and behaviors than a "Customer" in the support department. Rather than force them into one bloated model, bounded contexts let each area maintain its own focused, appropriate model.
Techniques for Identifying Contexts
Language Analysis
Listen to how different teams talk. When the same term means different things to different groups, you've found a context boundary. Sales talks about "converting leads," while billing discusses "invoicing customers"—these suggest separate contexts.
Organizational Boundaries
Teams, departments, and reporting structures often naturally align with bounded contexts. If two groups rarely collaborate and serve different purposes, they likely need separate models.
Business Capabilities
Map what your business does: order management, inventory, shipping, customer relations. Each major capability is a candidate for its own bounded context with its own models and rules.
Model Tension Points
When adding a feature requires awkward compromises or conflicts with existing model assumptions, you've likely crossed into another context. If your "Order" model keeps growing with conflicting concerns, it may span multiple contexts.
Key Takeaway: Bounded contexts emerge from careful analysis of how language, organizational structure, and business capabilities naturally divide your domain—don't force artificial unification when different areas genuinely need different models.