What if microservices had nothing to do with technology?
summary
Examines organizational and team-design aspects related to microservices rather than implementation details, covering topics like team topology, roles, communication and coordination. Uses examples of organizational changes tried and implemented at Docker to illustrate approaches and trade-offs, and shows how those lessons apply even when not using microservices.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:21Microservices vs Monoliths vs...
- 3:37What You Won’t Find Here
- 6:40Definition
- 7:36Why This Law Matters?
- 8:57We Always Have a Choice
- 11:13Communication Between Services
- 12:43Communication?
- 22:07Cognitive Load
- 23:36Ownership
- 24:52Diversity
- 25:09Team, Not Individuals
- 26:22Responsibilities
related talks
01h 02mDesigning Microservices
49mMicroservices: An unexpected Journey
39mThe Human Side of Microservices
32mThe right questions to ask when using microservices
48mDesign principles to the rescue of micro-services
37mKnee Deep in Microservices
48mMicroservices - Opportunities, Dilemmas and Problems
42mPitfalls of Microservice Architecture