Balancing Coupling: Future-Proof Your Software Architecture скачать в хорошем качестве

Balancing Coupling: Future-Proof Your Software Architecture

Are you struggling with the complexity of highly coupled systems or the pitfalls of over-decoupling? In this InfoQ podcast, Thomas Betts interviews Vlad Khononov, author of "Balancing Coupling in Software Design," to reveal the nuanced approach to effective software architecture. Timestamps: 0:00 Introduction 1:07 Balance coupling is the goal, not no coupling 3:35 If the outcome can only be discovered by action and observation, it indicates a complex system 7:23 Three dimensions of coupling 9:49 Distance and knowledge sharing are intertwined 13:04 Coupling is only a problem if a component is volatile 16:22 Distance affects where code lives as well as the lifecycle to maintain related components 19:10 Four levels for measuring coupling 24:51 Examples of the four types of coupling 28:01 Modularity is the opposite of complexity 29:19 Modular monoliths can reduce complexity 31:45 If shared knowledge is appropriately high, then balance it with distance 33:35 Evaluating volatility requires understanding the business domain 36:13 Balancing the three dimensions of coupling 40:57 Wrapping up 🔗 Transcript available on InfoQ: https://bit.ly/4i3aNnW #SoftwareArchitecture #Coupling #Scalability 🔔 Like this video if you found it valuable and subscribe for more insights on software architecture and design! 💬 What are your biggest challenges in balancing coupling in your systems? Share your experiences in the comments below! 👇