Sociotechnical Architecture: What Drives Software Architecture & Teams
summary
The talk examines how socio-technical architecture affects software architecture and team organization as systems evolve into microservices. It discusses Domain-Driven Design’s strategic design (especially Bounded Contexts) and the guideline “a microservice is owned by one team,” warning there’s no one-size-fits-all blueprint and outlining risks and impacts these choices can have on both systems and organizations.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:09About me
- 2:42Hypoport AG
- 5:36From idea to project
- 6:07Let's work together!
- 14:33Dunbar's number
- 20:35Component
- 22:26Feature
- 26:11Team Cognitive Load
- 27:50Team Topologies team types
- 29:12Team Topologies interaction forms
- 29:53Domain-Driven Design (DDD)
- 31:59Splitting boundaries
- 32:46Conclusion
related talks
32mCollaboration in Socio-Techinical Systems
35mOrganization: A Tool for Software Architects
45mTeam and Software: Making an Impact as an Architect
45mAdaptive Socio-Technical Systems
43mAdaptive Socio-Technical Systems with Architecture for Flow
43mAdaptive Socio-Technical Systems with Architecture for Flow
46mArchitecture for Cross-Functional Teams
46mAdaptive Socio-Technical Systems with Architecture for Flow