Microservices: A retrospective
summary
Microservices are pitched as velocity, scale and resilience but the real payoff is organizational scaling: teams gain independence and less synchronization. Lessons: keep very small APIs and avoid shared datastores; automate deploys with infrastructure as code (Terraform), deployment tooling (Spinnaker) and monitoring stacks (ELK, New Relic); learn distributed “laws of physics” (Lamport, CAP). Practical wins come from event patterns — event sourcing and sagas — which increase observability, enable eventual consistency, and make large systems simpler and more resilient.
AI-written summary · about
chapters (13)
- 0:00Intro
- 3:36Why do Microservices?
- 10:26Let me explain
- 16:53Small is Good
- 19:55Polyglot Ahoy
- 23:06Conway Knows
- 25:09Operations Matter
- 28:36The Laws of Physics
- 31:12Observability
- 35:48Quick Recap
- 36:42Events
- 42:24Commoditization
- 43:54Further Reading
related talks
52mMicroservices: A Utopian Mystery
49mMicroservices: An unexpected Journey
38mMicroservices, a bittersweet symphony
26mMicroservices
01h 03mThe Magic of Small Things - 10 Years of Microservices
44mIs It Time Already? Microservices Are Dead; Long Live Microservices!
27mThe technical journey to microservices
26mCreating a scalable ecosystem of Microservices
