Completed
3:35 If the outcome can only be discovered by action and observation, it indicates a complex system
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Balancing Coupling: Future-Proof Your Software Architecture
Automatically move to the next video in the Classroom when playback concludes
- 1 0:00 Introduction
- 2 1:07 Balance coupling is the goal, not no coupling
- 3 3:35 If the outcome can only be discovered by action and observation, it indicates a complex system
- 4 7:23 Three dimensions of coupling
- 5 9:49 Distance and knowledge sharing are intertwined
- 6 13:04 Coupling is only a problem if a component is volatile
- 7 16:22 Distance affects where code lives as well as the lifecycle to maintain related components
- 8 19:10 Four levels for measuring coupling
- 9 24:51 Examples of the four types of coupling
- 10 28:01 Modularity is the opposite of complexity
- 11 29:19 Modular monoliths can reduce complexity
- 12 31:45 If shared knowledge is appropriately high, then balance it with distance
- 13 33:35 Evaluating volatility requires understanding the business domain
- 14 36:13 Balancing the three dimensions of coupling
- 15 40:57 Wrapping up
