Context Mapping Patterns

Partnership, Customer/Supplier, ACL, Conformist, Shared Kernel.

0/2 done

Theory

Once you've drawn your contexts, the relationships between them become first-class design decisions:

PatternWhat it means
PartnershipTwo contexts evolve together, mutual commitment.
Customer / SupplierUpstream serves downstream; downstream has a voice.
ConformistDownstream takes whatever upstream provides — no negotiation.
Anti-Corruption Layer (ACL)Downstream wraps upstream behind its own model.
Shared KernelA small, jointly owned shared model. Expensive — use sparingly.
Open-Host Service / Published LanguageUpstream publishes a stable protocol.

Reflect

Map your current system's contexts.

  • Which edges are Partnerships you'd rather break?
  • Where would an ACL stop a leak you keep patching?

Reading in progress · 0 of 2 activities done