Adaptive Systems with Domain-Driven Design, Wardley Mapping, and Team Topologies: Architecture for Flow

Part I: Business Strategy with Wardley Maps1: The Landscape of a Wardley Map2: Patterns & Principles of a Wardley MapPart I Summary: Understanding the Importance of Wardley Maps for Business StrategyPart II: Designing Services with Domain-Driven Design and Wardley Maps3: Strategic Design as Part of the Value Chain4: Use Case Example: Strategically Designing a Conference Solution5: Tactical Design as Part of the Value ChainPart II Summary: How Wardley Maps Help to Visualize Domain-Driven DesignPart III: Implementing Services with Domain-Driven Design6: Overview of the Building Blocks of Domain Models7: Applying Hexagonal Architecture8: Use Case Example: Implementing a Conference Solution in TypeScript with DDD and Hexagonal ArchitecturePart III Summary: How to Build Adaptive Services with DDD and Hexagonal ArchitecturePart IV: Deploying and Operating Services9: Overview of Infrastructure and Operational Complexities10: Mapping Infrastructure and Operational Complexities onto a Wardley MapPart IV Summary: The Infrastructure and Operational Challenges Visualized by a Wardley MapPart V: Evolving Services with Wardley Maps11: Mapping Open-Source Software12: Mapping Container Orchestration13: Mapping Serverless TechnologiesPart V Summary: How Adaptive, Evolvable Services are Optimized for Fast Flow of ChangePart VI: Team Organization14: Culture of Pioneers, Settlers and Town Planners15: The Impact of Conway's Law16: Fundamental Team Topologies and Team Interaction Modes17: Mapping Team TopologiesPart VI Summary: How to Organize Teams for Fast Evolution