Scale, Microservices and Flow
summary
Argues that universal scaling laws from the Santa Fe Institute explain why hierarchies slow organisms and companies (metabolic-rate exponent 3/4), why listed firms show ~0.85 revenue scaling as they double, and why Amazon shows 1.15 superlinear revenue per head by adopting small‑world, two‑pizza team patterns and service boundaries. Recommends tracking the four DORA metrics (deploys, lead time, MTTR, change‑failure) as leading indicators of organizational health and shows that creating many weakly coupled teams (Spotify/AWS style) enables superlinear growth.
AI-written summary · about
chapters (10)
- 0:00Introduction and inspiration
- 2:37Corporate metabolism explained
- 10:42Complex adaptive systems overview
- 20:20Scaling laws in nature and companies
- 27:52Signs of organizational aging
- 31:31Corporate mortality and risks
- 33:21How to make more money than God
- 38:34Cities and super-linear growth
- 42:26Takeaways and future implications
- 47:51Q&A and closing
related talks
37mScale, Flow and Microservices
42mScale, Flow and Microservices
44mFlow, microservices and scale｜
49mSoftware Architecture, Team Topologies & Complexity Science
53mKeynote - Software Architecture, Team Topologies and Complexity Science
39mTeam Topologies, Software Architecture & Complexity
01h 01mSoftware Architecture, Team Topologies & Complexity Science
58mScaling like a Silicon Valley startup