82,891
edits
Tight coupling: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{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 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. | {{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 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 {{author | Originates from {{author|Charles Perrow}}’s {{br|Normal Accidents}}. | ||
Tightly coupled systems include Dams, power grids, nuclear power stations, aeroplanes and DNA. | |||
Loosely coupled systems include post offices, universities, research and development and most manufacturing. | |||
===Features of tight and loose coupling=== | ===Features of tight and loose coupling=== | ||