Keynote - Software Architecture, Team Topologies and Complexity Science

on YouTube ↗53m

" summary

Research ties microservices, Team Topologies and complexity science to measurable scaling laws: typical companies show sublinear revenue scaling (~0.85) while Amazon shows 1.15 exponent (gets easier to get bigger), explained by small‑world team networks and hierarchical fractal limits. Concrete practices cited: strict API interfaces, design interfaces “to sell”, two‑pizza / Dunbar-sized teams, four/five DORA metrics (lead time, MTTR, change failure rate, deploy frequency, scalability), and four Team Topologies archetypes (streamlined, enabling, complicated subsystem, platform). Value‑stream maps and queues are shown as the real blockers.

AI-written summary · about

" chapters (12)

1. 0:00Start
2. 14:57Team Topologies
3. 15:49Melvin Conway
4. 18:53Value and Flow
5. 22:11What Is Value
6. 30:23The Study of Complex Adaptive Systems
7. 37:08Invariant Terminating Units
8. 38:55Corporate Metabolism
9. 41:19Hierarchical Fractal Networks
10. 45:38Recap on Corporate Metabolism
11. 49:45Organizational Mortality
12. 52:07Scaling Complex Adaptive Systems

" related talks

• 49mSoftware Architecture, Team Topologies & Complexity ScienceJames Lewis · YOW! Melbourne 2022
• 39mTeam Topologies, Software Architecture & ComplexityJames Lewis · GOTO Amsterdam 2022
• 01h 01mSoftware Architecture, Team Topologies & Complexity ScienceJames Lewis · YOW! 2021
• 42mScale, Flow and MicroservicesJames Lewis · GOTOpia Chicago 2021
• 48mScale, Microservices and FlowJames Lewis · Build Stuff 2019
• 37mScale, Flow and MicroservicesJames Lewis · GOTOpia February 2021
• 44mFlow, microservices and scale｜James Lewis · Øredev 2019
• 39mKeynote - The gordian knotAlberto Brandolini · Voxxed Days Ticino 2018