Making microservices a behaviour not a buzzword
summary
Microservices require a concrete business goal: reduce deployment time, improve resilience, or enable geographic scale. Examples cited: Amazon cuts releases to every 11.7 seconds, Netflix adopts services for graceful failures, Uber rearchitects to enter new territories. Practical stack items are Docker and Kubernetes, API gateways, CI (Jenkins/Maven) and contract specs like Swagger and dev portals; expect thousands or tens of thousands of services and organize cross-functional pods, self‑serve access and telemetry to prove value.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:40Why microservices
- 5:36Main strategy
- 7:10Technology
- 10:45The nature of services
- 12:11User adoption
- 13:46Easy things to do
- 15:27The divide
- 20:55Business outcomes
- 23:01Metrics
- 23:57Summary
