Capability Mapping

on YouTube ↗55m

" summary

Argues that microservices must align to business processes (not just vague domains) to get independent deployability and avoid the entity-service anti‑pattern. Recommends finding boundaries with value stream mapping and event storming, targeting processes or activities as services, using events/AMQP for low coupling and HTTP/gRPC when near‑real‑time is needed. Warns against nano‑services and ESBs, aims for roughly 80% product mode / 20% project mode so teams ship independently.

AI-written summary · about

" chapters (24)

1. 0:00Intro
2. 0:29Agenda
3. 1:54Why Microservices?
4. 2:50Monoliths Do Not Scale To Many Teams!
5. 6:50Microservices let us scale an organisation
6. 8:36Independent Deployability
7. 9:12Product Mode
8. 12:36A Brief History of Microservices
9. 20:01Microservices are partitions of software
10. 22:12Microservices require Common Closure
11. 22:54Microservices need stable partitions
12. 24:50Cohesion and Coupling
13. 25:52Splitting Up Services
14. 26:56SOA is Aligned to Processes
15. 28:29Process & Capability
16. 30:03Finding Processes
17. 30:34Value Stream Mapping
18. 38:55Guest Cycle
19. 40:35Smart Endpoints and Dumb Pipes
20. 42:17Multitudes, Multitudes
21. 43:06Event Storming
22. 48:33Microservices are Bounded Contexts!
23. 50:33Inside the Microservice Boundary
24. 52:40Across Microservice Boundaries

" related talks

• 01h 01mCapability MappingIan Cooper · NDC London 2020
• 42mCapability MappingIan Cooper · Build Stuff 2020
• 49mMicroservices: An unexpected JourneySam Newman · JavaDay Ukraine 2017
• 49mIdentifying and Scoping MicroservicesChristian Horsdal · DevConf 2019
• 38mMicroservices, a bittersweet symphonySebastian Sogamoso · RailsConf 2015
• 30mThe Entity Microservice Trap: You May Be Doing It WrongFred George · GOTO Chicago 2016
• 58mFinding your service boundaries - a practical guideAdam Ralph · NDC Oslo 2018
• 01h 02mDesigning MicroservicesVenkat Subramaniam · Great International Developer Summit 2025