ArchitectureSystem Design
KW-0071Tight Coupling
Problem
Meaning
design where components are highly dependent on each other, making changes difficult and risky
Example
“Changing one module requires updating multiple other modules due to direct dependencies”
Reference
Avoid in scalable systems; leads to fragile and hard-to-maintain code
Related
loose couplingdependencyrigidity