Decomposing for Change
Architects should focus on decomposing systems based on volatility, encapsulating areas of potential change to contain risks effectively. This approach prevents widespread disruption when changes occur, contrasting sharply with functional decomposition, which can lead to catastrophic failures. Recognizing common areas of volatility and their interactions can streamline design efforts, promoting a more resilient architecture.In this clip
From this podcast
Software Engineering Radio - the podcast for professional software developers
Episode 407: Juval Lowy on Righting Software
Related Questions