Capability Mapping
summary
Claim: partition services by business capability so teams reach independent deployability and ship in hours instead of weeks. Methods: use value stream mapping and event storming to find handoff points and candidate boundaries, aiming for 5–15 steps per value stream and teams of ~4–7 people. Engineering rules: prefer events over entity services, expose explicit APIs, expect a microservice to span multiple processes (not one container), and use off‑the‑shelf models like APQC to jump‑start the map.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:49What is Capability Mapping
- 1:25Brighter
- 1:44Agenda
- 2:34Speed Wins
- 3:30Old School Model
- 7:02Independent Deployability
- 10:05Componentization
- 10:33SOAP
- 12:37Boundaries
- 15:00Strong Cohesion
- 15:38Microservice Definition
- 18:02Business Process Alignment
- 18:14Value Stream Mapping
- 19:37Walk the Floor
- 20:10Look for Handoffs
- 20:29Granularity
- 21:58Customer
- 25:56Activities
- 28:02Entity Services
- 28:35Valuestream Mapping
- 29:21Event Storming
- 32:30Looking for Boundaries
- 35:13Boundary Context
- 36:42Bounded Context
- 38:10Microservices
related talks
01h 01mCapability Mapping
55mCapability Mapping
30mFight the big ball of mud with business capability mapping
47mMicroservices and the Inverse Conway Manoeuvre
49mIdentifying and Scoping Microservices
26mDrawing the right lines: DDD, APIs and Microservices
58mMicroservices and the Inverse Conway Manoeuvre
32mSplitting the monolith