Software Engineering · Architecture
The degree to which one component depends on another's internals — the tighter the coupling, the more a change on one side risks breaking the other.
Example: Billing code that directly reads fields from the user-profile table breaks if that table changes.
In practice: Teams usually reduce coupling by communicating through a stable API or event contract instead of reaching into another service's internal data model directly.