How I Finally Stopped Worrying & Learnt to Love Conway’s Law
summary
Conway’s Law predicts architectures mirror organization, and this is shown with concrete numbers and fixes: a ticketing e‑commerce project with ~200/100 offshore teams turns into a distributed monolith that requires lock‑step releases; teams that avoid crossing boundaries cut wait time from ~8 days (23‑day cycle) to ~0 (2‑day cycle). Reorganizations into cross‑functional lines of business, 10–20 person teams and ~160–200 person value streams enable independent deploys, continuous delivery and reduce the need for heavy practices like consumer‑driven contracts and the microservice stability onion.
AI-written summary · about
chapters (5)
- 0:00Start
- 15:55beware the distributed monolith
- 21:56Cross-functional teams single purpose
- 26:58DEVOPS!!!
- 34:53The microservice stability onion
related talks
58mMicroservices and the Inverse Conway Manoeuvre
01h 00mMicroservices and the Inverse Conway Manoeuvre
46mLeading Distributed Teams
49mConway's Law: When Best Practices Are Not Enough
57mDomain Architecture Isomorphism and the Inverse Conway Maneuver
50mConway's Law: When Best Practices Are Not Enough
47mMicroservices and the Inverse Conway Manoeuvre
53mScaling Engineering by Hacking Conway's Law