Book Overflow Revenge of the Microservices! - Software Architecture: The Hard Parts
4 snips
Apr 6, 2026 They dig into service architecture strategy and when good plans backfire. They explain coupling vocabulary like afferent and efferent dependencies. They debate enforcing architecture with fitness functions versus pragmatic tradeoffs. They explore using LLMs to scaffold re-architecture and the risks of overtrusting AI. They discuss service granularity, team boundaries, and treating every line of code as liability.
AI Snips
Chapters
Books
Transcript
Episode notes
Pair Audiobook With Visual Materials
- Use the audiobook plus the PDF/Kindle concurrently for dense architecture texts that reference many diagrams.
- Nathan found the audiobook hard to follow because it repeatedly points to a 300-page PDF of diagrams, so read both to avoid confusion.
Two Coupling Metrics That Matter
- Afferent coupling counts incoming dependencies; efferent coupling counts outgoing dependencies.
- Afferent = how many things break if I change this; efferent = how many things I rely on not breaking.
Automate Architectural Governance
- Enforce architectural rules with automated fitness functions in CI to prevent erosion while you're away.
- ThoughtWorks-style metrics (acyclic graphs, coupling checks) can catch regressions that ADRs or meetings miss.
