Microservices, Where Did It All Go Wrong
summary
Argues that microservices often become distributed monoliths rather than independently replaceable components, creating latency, fragility and huge operational overhead; cites organizations ending up with 500–2,000 services and paying monitoring and orchestration bills in the millions. Points to common missteps: equating a microservice with a container or Lambda, replacing local calls with RPC chains, and poor domain partitioning. Gives concrete fixes: realign bounded contexts, prefer asynchronous messaging (Kafka) and sometimes collapse to a macro service or move from AWS Lambda to ECS for simplicity.
AI-written summary · about
chapters (6)
related talks
55mMicroservices, Where Did It All Go Wrong
01h 00mMicroservices, Where Did It All Go Wrong?
43mHow to Avoid Doing Microservices Completely Wrong
42mMicroservices are Not Worth the Trouble!!??
57mEmbracing Microservices
01h 05mPanel: Were Microservices a Huge Mistake?
54mThe Long Sad History of Microservices
53mDon’t Build a Distributed Monolith: How to Avoid Doing Microservices Wrong