Microservices
summary
Microservices split capabilities into separate processes so each service is independently deployable and upgradable, with per-service data stores (no shared DB), smart endpoints, dumb pipes, and decentralized language/toolchoice. Requires continuous delivery and infrastructure automation like blue-green deployment, rapid provisioning, monitoring and DevOps. Embraces design for failure (Netflix’s Chaos Monkey example) and often uses small teams (the two pizza teams idea). Trade-offs: easier independent release and availability but harder refactoring and consistency—eventual consistency becomes the norm.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:55Monolith vs. microservices
- 2:13Definition of microservices
- 3:14Characteristics of microservices
- 3:53Componentization via services
- 7:56Organized around business capabilities
- 9:19Decentralized data management
- 11:22Infrastructure automation
- 12:12Design for failure
- 13:22Are microservices just SOA?
- 15:45How big is a microservice?
- 17:49Monolith vs. microservices
- 24:04Conclusion
