How npm split a monolith and lived to tell the tale
summary
Argues that early architecture choices rarely matter and that the team first builds what delights users not a scalable final system, then faces a scaling crisis when success arrives. Describes migrating a single-process registry into a distributed system of separate services, making each component measurable, testable, and manageable, extracting functionality incrementally and validating via observable metrics and tests so the new microservices actually replace the monolith and let the service survive growth.
AI-written summary · about
related talks
01h 08mThrough Microservice Land with Node.js
50mEmbracing Microservices
33mA Monolith, a Microservices, and a Function Walk into a Bar
46mLove Your Monolith
01h 00mMicroservices, Where Did It All Go Wrong?
45mHow I learned to stop worrying and love the monolith
16mHow to prepare a distributed nodejs application
54mServices, Services, Everywhere!