Tight coupling

The Devil’s Advocate™ →Go uptown In which the curmudgeonly old sod puts the world to rights. Index — Click ᐅ to expand: The Devil’s Advocate Tell me more Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.

Not to be confused with the related concept in software architecture, tight coupling between two components of a distributed system, means that they are so closely interconnected or interrelated that the failure of one quickly or inevitably triggers failure of the other so that it is not practicable to shut the system down, isolate the failing component or otherwise reconfigure the wider system to operate safely before the failing components precipitate a catastrophic, system-wide failure.

Originates from Template:Author!Charles Perrow’s Normal Accidents.

Features of tight and loose coupling

Tight coupling	Loose coupling
Production delays not possible Difficult to stop the component operating Mandatory sequence of operation No scope for changing sequence on the fly Few buffers or redundancy in the system Existing buffers are hard-wired and inflexible Little scope for improvisation	Processing delays possible Production sequence can be changed Redundancy and slack on resources and personnel Fortuitous buffers and redundancies in the system Scope for improvision and substitution

See also

• Charles Perrow’s magnificent Normal Accidents, which introduced the concept of tight coupling in complex systems.
• DEPOSE components of a distributed system