Surviving microservices
summary
Adoption often yields lower velocity, performance regressions that need more hardware, higher defect rates and lack of visibility; root causes are concrete: overly fine-grained services, shared databases, lost messages and missing tracing. The sensible moves are measurable — measure lead time and count customer incidents — and practical: invest in monitoring/tracing, deployment automation and NFRs first, or consolidate into a hybrid monolith and use dashboards for proactive resolution.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:48Technical Due Diligence
- 6:31What Microservices Are
- 6:41Idea of a Microservices Architecture
- 10:26Design for Failure Approach
- 13:37Distribution and Microservices Architecture
- 15:40Lack of Solution Fit
- 18:07Performance
- 20:45Implementation Mistakes
- 23:55Mistakes in Encapsulation
- 33:09Hybrid Approach
- 36:20Seek External Guidance
related talks
57mEmbracing Microservices
45mMicroservices: A retrospective
28mSurviving in a Microservices Environment
45mResponsible Microservices
52mSurviving in a Microservices Team
45mBuilding and evolving microservices: lessons from the frontlines
27mThe technical journey to microservices
51mMicroservices for Mortals