Team topologies and the microservice architecture
summary
Argues that fast flow requires loose design‑time coupling and a fast automated pipeline; microservices scale teams of about five to nine by giving each service its own codebase, tech stack and deploy pipeline to avoid monolith bottlenecks. Recommends five supporting platforms (service foundation with service chassis and service template, observability, build, infra services, deployment) and tools like Crossplane for safe self‑provisioning and Flux/ArgoCD plus GitHub Actions for GitOps pipelines. Build the thinnest viable platform and evolve it.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker background
- 2:47Fast flow and feedback loops
- 6:19Team topologies principles
- 11:03Architecting for team topologies
- 20:00Monolithic vs microservices
- 24:43Microservices benefits at scale
- 30:59How team topologies aids microservices
- 36:00Key platforms for microservices
- 47:29Summary and conclusion
related talks
57mForking the Future: Embracing Microservices Evolution
21mAutonomous Teams
37mKnee Deep in Microservices
38mMicroservices, a bittersweet symphony
29mDevOps and Microservices Better Together
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
11mSAG Expert Interview #06: Enabling success with Microservices, Flow and Culture
26mCreating a scalable ecosystem of Microservices