Architecture for Flow - Wardley Mapping, DDD, and Team Topologies
summary
Claims that combining Wardley Mapping, Domain-Driven Design and Team Topologies lets teams evolve a legacy monolith into modular bounded contexts and cloud-hosted platforms to speed change. Uses Wardley maps to find streams of change, builds a platform team to execute serverless re-platforming, forms stream-aligned teams to refactor the “big ball of mud,” and applies event-storming for bounded contexts. Outcome is migrated infra, clear ownership boundaries, fewer handovers and lower team cognitive load enabling faster, continuous delivery.
AI-written summary · about
chapters (10)
- 0:00The systems thinking approach
- 1:08Building adaptive systems
- 2:44Analyzing legacy challenges
- 4:39Wardley mapping foundations
- 10:56Applying doctrinal principles
- 13:48Team topologies for flow
- 18:43Domain-driven strategic design
- 24:34Bounded contexts and architecture
- 32:47Implementing the transition
- 40:01Conclusion and takeaways
related talks
41mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
45mArchitecture for Flow with 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
43mAdaptive Socio-Technical Systems with Architecture for Flow