Balancing Coupling in Software Design
summary
Proposes an integration strength model with four concrete levels — implementation coupling, functional coupling, model coupling, and contract coupling — and defines maintenance pain as strength × volatility × distance. Uses DDD subdomains to measure volatility, shows microservice POCs succeed on low-volatility supporting subdomains but fail on core volatile domains, and accepts direct legacy DB access when volatility is effectively zero. Recommends eliminate accidental coupling, reduce strength to contracts or collapse distance when reduction is impossible.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:20Rethinking coupling
- 1:34The nature of coupling
- 3:44Defining the dimensions
- 8:30Historical models
- 10:26Structured design levels
- 14:22Conexions model
- 17:54Dynamic connections
- 20:48Limitations of old models
- 22:32Integration strength model
- 26:55Distance and volatility
- 30:54Subdomains and volatility
- 33:36Balancing the dimensions
- 37:09Practical examples
- 40:15Conclusion
- 42:13Q&A session
