SOLID in architecture
summary
Argues that SOLID scales to components with concrete rules: group classes by release equivalence and common-closure/reuse tradeoffs, choose a spot on Uncle Bob’s tension diagram so change affects few components, ban cycles via the acyclic dependency principle, measure instability with the fan-in/fan-out formula and keep dependencies toward stability, and align stability with abstractness. Demonstrates generating the instability/abstractness chart using PD Panth and recommends static analysis to detect pain zones and break cycles.
AI-written summary · about
chapters (7)
- 0:00The importance of architecture
- 2:29Defining software components
- 5:31Component cohesion principles
- 10:25Balancing architecture tension
- 12:47Acyclic dependency principle
- 16:39Stable dependencies
- 20:17Stable abstraction and metrics
related talks
01h 03mBreaking Dependencies: The SOLID Principles
51mSOLID Revisited : The State of the Matter
40mSOLID Architecture in Slices not Layers
41mUsing Boundary-Driven Development to beat code complexity
01h 29mArchitecture Beyond Clean & Hexagonal
51mA Contrarian View of Software Architecture
24mBuilding Software Architecture from First Principles
24mBuilding Software Architecture from First Principles