Balancing Coupling in Software Design: Universal Design Principles for Architecting Modular Software Systems
by Vlad Khononov
Preface
Books on software design typically dedicate a few pages to coupling. On rare occasions, you’ll find a whole chapter on the subject. Yet, while fads come and go, coupling has been, is, and, I bet, always will be relevant. Don’t believe me? Just take a moment and listen to the industry chatter. You will hear the “coupling is bad” mantra everywhere. But what exactly is this “coupling” thing? Is it always that bad, or does it become really bad after a certain point? Can you even measure it? If so, how? These are the questions I’ve sought answers to since I started working as a software engineer. All I encountered was more and more of “Avoid coupling!” or “This architectural pattern will save you from coupling!” or, even worse, “The only ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access