Microservices and the Inverse Conway Manoeuvre

on YouTube ↗01h 00m

" summary

Claim: organizational boundaries shape code, so deliberately redesign teams to change architecture. Reorganize into cross‑functional, long‑lived product teams around business capabilities, colocate with stakeholders, and push “build it run it” practices so services become cohesive and loosely coupled. Use async events and semantic versioning or consumer‑driven contract tests across organizational boundaries; prefer conversational change inside teams. Evidence: moving work across teams slows cycle time an order of magnitude (examples include 5 days of value vs 42 days waiting).

AI-written summary · about

" chapters (11)

1. 0:00Introduction to speaker
2. 4:56Conway's Law explained
3. 9:11Defining microservices
4. 12:25Organizational flow issues
5. 18:16Visualizing work flow
6. 23:54Anti-patterns in delivery
7. 30:00The OODA loop and teams
8. 36:24Reorganizing for success
9. 42:07Organizational design
10. 47:40Applying the architecture
11. 53:02Conclusion and Q&A

" related talks

• 58mMicroservices and the Inverse Conway ManoeuvreJames Lewis · NDC London 2017
• 47mMicroservices and the Inverse Conway ManoeuvreJames Lewis · NDC TechTown 2017
• 52mMicroservices & the Inverse Conway ManeuvreJames Lewis · GOTO Copenhagen 2015
• 57mDomain Architecture Isomorphism and the Inverse Conway ManeuverDylan Beattie · NDC Sydney 2016
• 09mDon’t Forget Conway’s LawSarah Novotny · O'Reilly Software Architecture Conference 2015
• 41mHow I Finally Stopped Worrying & Learnt to Love Conway’s LawJames Lewis · GOTO Chicago 2015
• 05mcultures and microservicesSarah Novotny · O'Reilly Software Architecture Conference 2015
• 46mWhy Cross-Functional Teams Build Better MicroservicesPeter-Gillard Moss · GOTO Copenhagen 2016