12 Loosely coupled software architecture
This chapter covers
- Minimizing coupling in software architecture
- Designing software architecture aligned to the domain
- Validating the design of individual subsystems
- Determining the optimal level of modernization for each subsystem
- Migrating subsystems from the current to the target state
Achieving independent value streams in software development requires a loosely coupled software architecture. Loose coupling in the software means lower change coupling across value streams, resulting in few organizational dependencies that affect flow. For some leaders, grasping the importance of loosely coupled architecture takes time. But there are no quick fixes to address the technical requirements of fast flow; ...
Get Architecture Modernization now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
