Don’t Forget Conway’s Law
summary
Conway’s Law drives the move from a monolith to microservices: a historical Amazon binary of 300–500 MB that takes 8–12 hour compiles forces organizational change, so leadership issues a two‑pizza teams rule and breaks the front page into few hundred microservices. A recommended path uses a small tiger team to extract single services, requires explicit API contracts and HTTP tooling like API gateways and NGINX, and succeeds only if teams adopt autonomy, accountability and public learning.
AI-written summary · about
chapters (3)
related talks
47mMicroservices and the Inverse Conway Manoeuvre
58mMicroservices and the Inverse Conway Manoeuvre
01h 00mMicroservices and the Inverse Conway Manoeuvre
52mMicroservices & the Inverse Conway Maneuvre
46mWhy Cross-Functional Teams Build Better Microservices
01h 03mThe Magic of Small Things - 10 Years of Microservices
44mThe Yellow Brick Road: Taking Microservices Home in Large Enterprises
47mMicroservices? Monoliths? An Annoying Discussion!
