Domain Architecture Isomorphism and the Inverse Conway Maneuver
summary
Argues that Conway’s Law explains why architecture fails and prescribes reorganizing people to match domain boundaries: one team per backlog and two-pizza teams that own interfaces (membership, publishing, casting). Shows concrete history: Spotlight’s shared SQL monolith, a failed skunkworks rewrite because teams didn’t communicate, then a move to HTTP/JSON APIs and async queues. Invokes Moore’s and Amdahl’s laws to justify removing blocking meetings and using queues/chaos tests (the chaos bus) so teams can scale and the system actually runs.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:43Ultimate Architecture Diagram
- 3:06Spotlight
- 4:37Melvin Conway
- 5:17Conways Law
- 5:59Whats an Organization
- 20:29Skunk Works
- 23:33Agile
- 27:04Teams
- 28:21Interfaces
- 30:25Membership
- 33:14Team Structure
- 35:41eCommerce Example
- 37:23Meeting Example
- 40:45Chaos Monkey
- 42:52Moores Law
- 49:31User Interface Design
- 57:01Outro
related talks
58mMicroservices and the Inverse Conway Manoeuvre
01h 00mMicroservices and the Inverse Conway Manoeuvre
49mConway's Law: When Best Practices Are Not Enough
40mThe (too) many faces of architecture
18mBuilding Platforms, Breaking Code How Your Org Chart Can Support or Wreck Progress
41mHow I Finally Stopped Worrying & Learnt to Love Conway’s Law
01h 02mThrough the Looking Glass
50mConway's Law: When Best Practices Are Not Enough