Architecture for Flow with Wardley Mapping, DDD, and Team Topologies
summary
Combines Wardley mapping + Domain‑Driven Design + Team Topologies to turn a monolithic online‑school prototype into modular bounded contexts, form stream‑aligned and platform teams, and migrate on‑prem services via re‑platforming to cloud then refactor with serverless. Shows concrete steps: map user needs to subdomains, assign single bounded context per team, use event‑storming and dynamic re‑teaming, create CI/CD and monitoring platforms. Claims this reduces cognitive load, closes an efficiency gap and yields measurably faster flow of change.
AI-written summary · about
chapters (9)
- 0:00Introduction to architecture for flow
- 2:34Combining three perspectives
- 4:20System thinking and Wardley Mapping
- 12:16Team Topologies for fast flow
- 16:57Architecture for flow with streams
- 22:56Domain-Driven Design basics
- 29:00Optimizing team ownership and platforms
- 37:06Transitioning to flow optimization
- 44:35Summary and resources
related talks
45mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
41mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
44mArchitecture for Flow - Wardley Mapping, DDD, and Team Topologies
43mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
43mAdaptive Socio-Technical Systems with Architecture for Flow
40mAdaptive Socio-Technical Systems with Architecture for Flow
46mAdaptive Socio-Technical Systems with Architecture for Flow