Microservices for Mortals
summary
Microservices come from Netflix/Amazon and work for business agility but cost upfront: expect an initial investment in service discovery, logging, metrics, CI/CD and much harder testing; Amazon pages run more than 100 microservices, which brings operational complexity. Use a separate database per service (CQRS/events to migrate), prefer REST for APIs but use messaging or websockets for heavy fan‑out, avoid shared binary libraries, align services with team boundaries (Conway’s Law), and design for failure with retries, caching, circuit breakers and horizontal instances.
AI-written summary · about
chapters (21)
- 0:00Intro
- 2:01Italian Food Analogy
- 4:24Where did it come from?
- 10:04What happened to SOA?
- 13:20Which pill do you take?
- 14:15blue pill world
- 16:43There is no spoon
- 17:42Welcome to red pill world
- 18:33About Monoliths
- 20:27When monoliths are bad
- 21:24Monolith to Microservices
- 22:45Initial Investment
- 25:25Data Strategy
- 28:40Synchronous vs Asynchronous
- 29:35Service Communication
- 31:19Avoid re-use traps
- 35:10Conway's Law
- 35:55What it actually means
- 41:29Design for Failure
- 45:27Some take-aways
- 48:57And one more thing...
