Making Sense Of Microservices
summary
Claims that microservices mainly amplify cognitive overhead and the false assumption "we know what we're doing," and proposes automation and chat-driven workflows to reduce that overhead. Describes using GitHub, CI/CD, Slack-style chat (chatops) to observe orient decide act, to surface exactly what needs attention, and to automate repetitive tasks like sprint zero automation and bulk security upgrades by opening hundreds of PRs across services; reports prototypes in use and optimistic results.
AI-written summary · about
chapters (10)
- 0:00Microservices hangover confession
- 4:05Modern developer challenge
- 8:26We don’t know what we’re doing
- 12:43Cognitive overhead problem
- 17:59Cognitive overhead in practice
- 24:07Sensible chat collaboration
- 26:56Automate busy work
- 30:31Focus on the reader
- 32:39Automate development loops
- 34:31Q&A and closing
related talks
38mMicroservices, a bittersweet symphony
01h 02mDesigning Microservices
39mThe Human Side of Microservices
37mKnee Deep in Microservices
44mIs It Time Already? Microservices Are Dead; Long Live Microservices!
52mI Have a Microservices Architecture and I Didn't Know.
24mThe misunderstood human resource management tool: Microservices Architecture
26mPros/Cons of Microservices