Capability Mapping
summary
Argues that real microservice boundaries come from automating stable business processes so teams can independently deploy and release many times per day instead of every two weeks or month. Recommends concrete techniques: value stream mapping to find customer-facing processes, event storming to find aggregates and shared events, and APQC process models for scale. Warns against CRUD “entity” services and central orchestration. Mentions using messaging platforms (Brighter / brightside) for inter-service integration.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 2:13Brightside
- 2:55Agenda
- 3:56Products not projects
- 4:30Adrienne Cockcroft
- 6:09Whats the problem
- 11:06Microservices
- 13:37Independent Deployability
- 13:58Product Mode
- 16:53Micro Services
- 22:23SOA
- 25:29Good microservices
- 26:59Stable partitions
- 27:43Stable boundaries
- 29:44Business capability
- 32:27Business process
- 35:43Value Stream Mapping
- 37:13Walk the Process
- 43:58Value Stream Mapping Exercise
- 48:07Empty Service Model
- 50:40Events
- 52:30Reservation Time
- 53:18Walkthrough
- 55:02Contexts
- 57:02Bounded Context
