Bounded Contexts: Team Topologies and Architecture boundaries aligned

on YouTube ↗47m

" summary

Argues that mapping domain, architecture and team structure together removes friction by splitting a subdomain (flight booking) into concrete bounded contexts — seat selection, payment, upgrades — and treating their interactions as only commands events data. Uses system thinking plus DDD to place contexts on a core-domain chart (value vs complexity), lists nine socio‑technical relationship patterns (customer‑supplier, partnership, shared kernel, open host, anti‑corruption layer), and extends Team Topologies with governing and vendor roles so teams align with upstream/downstream influence. Recommends anti-corruption layer for legacy/vendor integration.

AI-written summary · about

" chapters (12)

1. 0:00Introduction
2. 0:35Problem with misalignment
3. 1:40Conways Law
4. 7:29Cost and Software Development
5. 11:09Stability
6. 12:01Domains
7. 14:27Bounded Context
8. 16:41Payment example
9. 18:35Core domain charts
10. 27:30Abstract
11. 32:33Social and Technical Implications
12. 40:22Conclusion

" related talks

• 45mSystems Thinking by combining Team Topologies with Context MapsMichael Plöd · KanDDDinsky 2022
• 55mCharting the uncharted: Discovering and evolving bounded contextsPrem Chandrasekaran · DDD Europe 2025
• 51mDissecting Bounded Contexts -Nick Tune · DDD Europe 2020
• 43mArchitecture for Flow with Wardley Mapping, DDD, and Team TopologiesSusanne Kaiser · Agile meets Architecture Berlin 2022
• 43mAdaptive Socio-Technical Systems with Architecture for FlowSusanne Kaiser · Agile meets Architecture Berlin 2023
• 47mArchitecture for Flow with Wardley Mapping, DDD, and Team TopologiesSusanne Kaiser · KanDDDinsky 2022
• 44mArchitecture for Flow - Wardley Mapping, DDD, and Team TopologiesSusanne Kaiser · DDD Europe 2022
• 39mFrom Domain Boundaries to Software ArchitectureNick Tune, Maxime Sanglan-Charlier · Agile meets Architecture Berlin 2023