Tight Coupling

Definitions

1. A design condition where two modules depend heavily on each other's internal details — concrete classes, data structures, or execution order — making it difficult to change, test, or reuse one without modifying the other.

   In plain English: When two parts of a system are so intertwined that you can't change one without breaking the other.

   Example: "The billing service directly queries the user table instead of calling an API — that tight coupling means we can't change the schema without breaking billing."

Related Terms

• Loose Coupling
• Model-View-Controller
• Model-View-Presenter
• Model-View-ViewModel
• MVC
• Plugin Architecture
• Presenter
• Service Layer
• Code Organization