Responsible Microservices
summary
Argues for a checklist of concrete factors—multiple rates of change, independent lifecycles, and avoiding accidental complexity—then shows how to find candidates by mining git history and metrics (example: cyclomatic complexity thresholds where cyclomatic complexity >10 signals trouble) and by using tools like CodeScene. Demonstrates a strangler fig proxy that logs legacy requests, runs the new service in parallel, compares responses and falls back to the legacy path when mismatches occur, proving incremental replacement and safer rollout versus big‑bang rewrites.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 2:08Cloud to be clear
- 4:43Monoliths
- 6:14Microservices
- 8:18Characteristics
- 10:00Not Mjolnir
- 12:41Big Ball of Mud
- 15:00Modular Monolith
- 18:00Source Code Management
- 19:00Software Archaeology
- 26:30Data
- 28:20Independent Life Cycles
- 30:20Developer Productivity
- 35:20Focus on paved roads
- 36:10Get good at something
- 39:45Polyglot
- 40:58Interviewing Developers
- 42:32Sprawl
- 43:33Conclusion
- 44:46Questions
