Tight coupling

From The Jolly Contrarian
Revision as of 15:30, 31 August 2020 by Amwelladmin (talk | contribs) (Created page with "{{a|devil|}}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...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
In which the curmudgeonly old sod puts the world to rights.
Index — Click ᐅ to expand:
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.

See also