Microservices & the Inverse Conway Maneuvre

on YouTube ↗52m

" summary

Argues that organizing teams as stable, cross‑functional lines of business produces modular microservice architectures by design: examples include a retail/customer split across North America and Brazil using an async message bus, and an insurer that extracts home/motor/life into separate apps with separate data to avoid a distributed monolith. Claims work that stays inside a team finishes an order of magnitude faster (Australian telco data), targets services replaceable in days–weeks, and recommends consumer-driven contracts, tolerant reader, and Dumbar's number.

AI-written summary · about

" chapters (12)

1. 0:00Start
2. 0:19Two Characteristics of Micro Services
3. 7:04How Big Is a Micro Service
4. 19:26Lockstep Deployment
5. 20:34Distributed Monoliths
6. 23:15The Ooda Loop
7. 36:38Dunbar's Number
8. 37:49Graph of the Effect of Distance on Communication
9. 39:54Consumer-Driven Contracts
10. 40:29The Chunking Up from Micro Services to Teams to Value Streams
11. 41:41Semantic Versioning
12. 46:24If Data Is Kept Separate in each Micro-Service How about the Impact of Keeping the Data Consistent

" related talks

• 58mMicroservices and the Inverse Conway ManoeuvreJames Lewis · NDC London 2017
• 01h 00mMicroservices and the Inverse Conway ManoeuvreJames Lewis · NDC Oslo 2017
• 47mMicroservices and the Inverse Conway ManoeuvreJames Lewis · NDC TechTown 2017
• 26mPros/Cons of MicroservicesCassandra Shum · Microservices Day London 2017
• 09mDon’t Forget Conway’s LawSarah Novotny · O'Reilly Software Architecture Conference 2015
• 50mEmbracing MicroservicesGrzegorz Piwowarek · Build Stuff 2024
• 38mMicroservices, a bittersweet symphonySebastian Sogamoso · RailsConf 2015
• 46mWhy Cross-Functional Teams Build Better MicroservicesPeter-Gillard Moss · GOTO Copenhagen 2016