Software Architecture, Team Topologies & Complexity Science

on YouTube ↗49m

" summary

Argues that scaling follows measurable laws: Amazon shows a 1.15 exponent of revenue vs employees (superlinear growth), cities show both superlinear innovation and sublinear infrastructure costs, and three principles (hierarchies, invariant units, optimization) explain those laws. Demonstrates that self‑service infrastructure (AWS style) removes queues, that change request boards predict low organizational performance, and that monitoring DORA metrics gives a health signal. Recounts building simulators to test these ideas and promotes using two‑pizza teams and Team Topologies as forcing functions for value flow.

AI-written summary · about

" chapters (15)

1. 0:00Intro
2. 5:09What is value?
3. 11:59Team Topologies
4. 14:05The curious case of Amazon
5. 16:22Complexity & flow
6. 17:01Complex adaptive systems
7. 21:553 simple principles
8. 22:59Complex adaptive systems are everywhere
9. 23:29Corporate metabolism
10. 26:39Sidebar: Identifying the signs of ageing
11. 33:11Scaling complex adaptive systems
12. 44:59Summary
13. 46:09Resources
14. 46:25Outro
15. 46:50Q&A

" related talks

• 01h 01mSoftware Architecture, Team Topologies & Complexity ScienceJames Lewis · YOW! 2021
• 39mTeam Topologies, Software Architecture & ComplexityJames Lewis · GOTO Amsterdam 2022
• 53mKeynote - Software Architecture, Team Topologies and Complexity ScienceJames Lewis · NDC Porto 2022
• 48mScale, Microservices and FlowJames Lewis · Build Stuff 2019
• 37mScale, Flow and MicroservicesJames Lewis · GOTOpia February 2021
• 42mScale, Flow and MicroservicesJames Lewis · GOTOpia Chicago 2021
• 44mFlow, microservices and scale｜James Lewis · Øredev 2019
• 45mTowards Architecture Organization Topologies for Sustainable Fast Flow of ChangeEduardo Da Silva · Agile meets Architecture Berlin 2023