Implementing Domain-Driven Design (Study Group) Chapter 3 - Context Maps.
Content :
Recap Bounded Context
Found Subdomain & Bounded Contexts is Enough?
Issue 1: More Complex Scenario, More Unclearly Bounded Context
Issue 2: Organization Complexity
Issue 3: Large team size or multiple development teams
Issue 4: Distributed or offshore team
Issue 5: External, Separate Systems
Issue 6: Legacy Systems
What is Context Maps?
Context Maps Description
Upstream and Downstream
The helping from Context Maps
The Benefit for Drawing Context Maps
The relationship for Context Maps
Is this important for the relationship?
Discovering potentially crisis
Helps to integrate different bounded contexts with other teams
Relationship Patterns for Context Maps
1. Shared Kernel
2. Partnership
3. Customer – Supplier
4. Conformist
5. Separate Way
6. Big Ball of Mud
7. Anticorruption Layer (ACL)
8. Open Host Service (OHS)
9. Public Language (PL)
Example – DDD Cargo Sample
Example – Insurance Company
Mapping the IDDD Three Bounded Context - SaaSOvation
Recap Three Bounded Context Product
Collaboration Context Mapping Example
Code Implementing for Context Maps Representation
OHS/PL and ACL for Implementing.
Collaboration Context with Identity & Access Context
Autonomy - Value Object for a minimal amount of state
Agile PM Context with Identity & Access Context
Agile PM Context with Collaboration Context
Dependent on other Context to do Action issue
Solution Method – Standard Type for Value Object
Recap Chapter 3 - Context Maps