The Human Side of Microservices
summary
Argues microservices are primarily a human and organizational pattern, not just technology, citing Conway's law: org communication shapes architecture and insisting teams need autonomy plus clear ownership to release, run and monitor their services. Specifies required runtime features: service auto-discovery, redundancy, fault tolerance and self‑healing, and operationally ties microservices to DevOps and documentation-as-contract. Notes surprising churn metric — 11-month average startup tenure — and promotes thin‑slice teams and full‑stack JavaScript/Node.js as practical enablers of independent services and faster deployments.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:25Who am I
- 3:42Why Code
- 7:53Microservices Architecture
- 10:45Decoupling
- 12:13DevOps
- 13:42Peace
- 14:35Power Struggle
- 15:57Generation Y
- 21:26Microservices
- 24:12How can we succeed
- 27:22Microservices and communication
- 29:09Documentation
- 32:48Mode of Ownership
- 37:36Conclusion
related talks
49mMicroservices: An unexpected Journey
38mMicroservices, a bittersweet symphony
05mcultures and microservices
44mIs It Time Already? Microservices Are Dead; Long Live Microservices!
01h 02mDesigning Microservices
36mThe human factor you might be missing when designing your system
45mMicroservices: A retrospective
24mThe misunderstood human resource management tool: Microservices Architecture