Discover the nuanced approach to effective software architecture in this 42-minute InfoQ podcast where Thomas Betts interviews Vlad Khononov, author of "Balancing Coupling in Software Design." Learn why balanced coupling—not zero coupling—should be your goal when designing software systems. Explore the three dimensions of coupling, understand how distance and knowledge sharing are intertwined, and discover why coupling only becomes problematic with volatile components. The discussion covers four levels for measuring coupling with practical examples, explains why modularity counteracts complexity, and demonstrates how modular monoliths can reduce system complexity. Gain insights on evaluating volatility through business domain understanding and strategies for effectively balancing coupling dimensions to create future-proof software architecture. The podcast includes a comprehensive breakdown of topics from the fundamentals of coupling to practical implementation strategies for complex systems.
Balancing Coupling: Future-Proof Your Software Architecture
Overview
Syllabus
0:00 Introduction
1:07 Balance coupling is the goal, not no coupling
3:35 If the outcome can only be discovered by action and observation, it indicates a complex system
7:23 Three dimensions of coupling
9:49 Distance and knowledge sharing are intertwined
13:04 Coupling is only a problem if a component is volatile
16:22 Distance affects where code lives as well as the lifecycle to maintain related components
19:10 Four levels for measuring coupling
24:51 Examples of the four types of coupling
28:01 Modularity is the opposite of complexity
29:19 Modular monoliths can reduce complexity
31:45 If shared knowledge is appropriately high, then balance it with distance
33:35 Evaluating volatility requires understanding the business domain
36:13 Balancing the three dimensions of coupling
40:57 Wrapping up
Taught by
InfoQ
