Microservices and the Inverse Conway Manoeuvre
summary
Claim: software boundaries become team boundaries, so reorganizing teams reshapes architecture. Evidence: studies (Allen, Conway, Dunbar) and a ThoughtWorks case show user stories that leave a team cycle an order of magnitude slower. Practice: split by business capabilities, create long‑lived product teams owning data and messaging (Compare the Market), add site‑reliability/self‑service infra, use semantic versioning, consumer-driven contracts or tolerant‑reader patterns at appropriate boundaries. Result: fewer queues, much lower cycle time, clearer ownership — the Inverse Conway Manoeuvre in action.
AI-written summary · about
chapters (4)
related talks
01h 00mMicroservices and the Inverse Conway Manoeuvre
47mMicroservices and the Inverse Conway Manoeuvre
52mMicroservices & the Inverse Conway Maneuvre
57mDomain Architecture Isomorphism and the Inverse Conway Maneuver
09mDon’t Forget Conway’s Law
41mHow I Finally Stopped Worrying & Learnt to Love Conway’s Law
46mWhy Cross-Functional Teams Build Better Microservices
05mcultures and microservices