Microservices Highway to hell
summary
Builds a global social network aiming for 1M users requirement and uses Azure, Docker Swarm, Spring Cloud, Couchbase with CDN and Git-based config. Team of four developers plus one ops hits seven key failures: heavy component sprawl, cache inconsistency across instances for user timelines, DTO coupling from a shared library, duplicated load‑balancing (Ribbon vs proxy), deployment races with a measured 10s Eureka registration lag, and brittle Azure CLI/API automation that forces manual rewrites. Recommendations: start tiny, assign per‑service owners, expect failures.
AI-written summary · about
chapters (5)
- 0:00Start
- 7:11Deploying a new version of a microservice works seamlessly and problem free.
- 10:17Guess how a component is working
- 15:07Small team working on every microservices
- 17:41Blind trust the cloud provider API stability
related talks
01h 01mMicroservices Gone Wrong
35mSeven years with microservices: a critical review
01h 00mMicroservices, Where Did It All Go Wrong?
39m10 Tips for failing at microservices
57mEmbracing Microservices
55mMicroservices, Where Did It All Go Wrong
53mPowering 100+ million daily users
51mBig microservices, small team a painful story