How to f*ck Up Your Development Team with Microservices
summary
Stephan recounts his experience building a large e-commerce system with a microservices architecture, highlighting concrete downsides like increased complexity, high individual responsibility, and many new technologies. He explains how these factors make life harder for developers, operators, and project managers, cause team dissatisfaction, and lead to underestimated resource and maintenance costs.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:39Microservices complexity
- 14:03Local dev and debugging
- 21:21Team structure and communication
- 25:33Frustration and solutions
- 33:30Organization and scaling
- 37:52Review and recommendations
- 41:13Conclusion and Q&A
related talks
55mMicroservices, Where Did It All Go Wrong
01h 00mMicroservices, Where Did It All Go Wrong?
44mMicroservices, Where Did It All Go Wrong
43mPanel: Microservices, Where Did It All Go Wrong
39m10 Tips for failing at microservices
01h 01mMicroservices Gone Wrong
56mHow to Survive with Microservices
42mMicroservices are Not Worth the Trouble!!??