Loose Coupling: Difference between revisions

From CasGroup
Jump to navigationJump to search
Eboxytezi (talk | contribs)
No edit summary
m Reverted edits by Eboxytezi (Talk) to last version by Jfromm
 
Line 18: Line 18:
interface.
interface.


>== References ==
== References ==


[http://dev2dev.bea.com/pub/a/2004/02/orchard.html Achieving Loose Coupling], David Orchard
[http://dev2dev.bea.com/pub/a/2004/02/orchard.html Achieving Loose Coupling], David Orchard
----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://ewozukyn.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
----
=[http://ewozukyn.co.cc CLICK HERE]=
----
</div>

Latest revision as of 16:46, 11 February 2011

Loose coupling means low dependency between two systems. It is a way to achieve high fault tolerance and often used in association with Web Services and Service-Oriented Architecture (SOA). Loosely coupled systems are not strongly connected with each other, they have only a minimal coupling between the components in the system. They are obviously the opposite of tightly coupled systems with strong dependencies between the components. In loosely coupled systems, there is a low probability that changes within one module or component will create unanticipated changes within other modules or components. The modular approach to design and develop systems associated with loose coupling makes the applications more agile and flexible, and enables quicker change. A common way to achieve low coupling is to use interfaces and messages: one module does not have to be concerned with the internal implementation of another module, and interacts with another module with a stable interface.

References

Achieving Loose Coupling, David Orchard