Context Maps - a deep dive
summary
Context maps deliver a practical map of how bounded contexts and teams actually interact, exposing which models propagate (loan application form → scoring), where code or schemas are Shared Kernel, and where team power creates upstream/downstream or customer–supplier constraints that block releases. Patterns spelled out include Open Host Service, Conformist, Anti-Corruption Layer and Big Ball of Mud. The claim is concrete: mapping these relationships surfaces hidden politics and model contagion, so modernization plans target anti‑corruption layers or rework shared artifacts rather than refactoring blindly.
AI-written summary · about
chapters (26)
- 0:00Intro
- 4:28McKinsey study
- 6:16Linguistic differences
- 7:13Coupling
- 9:20Technical aspects
- 10:07Domain events
- 11:14Decoupling
- 12:29Communication
- 14:06Context Maps
- 19:06Open Host Service
- 25:23AntiCorruption
- 27:18Coordinate
- 28:55Customersupplier
- 30:05Integration
- 30:50Separate Ways
- 31:35Published Languages
- 32:51Open Host Services
- 33:53Big Bowl of Map
- 35:19Shared Kernel
- 36:29Published Language
- 37:59Team Relationships
- 39:25Real World Example
- 40:17Anti Corruption
- 42:13Model Problem
- 43:38Influence
- 46:45Banking systems
related talks
30mContext is All You Need: The Art and Science of Information Design
27mMapping Complex Systems to Find Problems and Solutions
41mMapping Experiences: From Insight To Action
53mContext, Bloody Context
39mDo the Next Right Thing
53mValue Mapping: Building Understanding, Communicating the Benefits of What You Do
40mArchitecture Modernization with DDD
47mThe product confidence trap