Hi Chiru,
I hope that below extract will help you out:
<b>What is coupling</b>:Coupling is a term that describes the level of common knowledge necessary by a provider and a consumer in a distributed computing exchange.
<b>Tight Coupling</b>:In a tight coupling exchange, the programmer of one participant (say, the consumer, or client) must have detailed knowledge about the behavior, such as the method calls, messaging protocol, synchronous behavior, or message semantics, of the other participant (in this case, the provider, or server) in order to successfully complete the required interaction between the two pieces of software.
<b>Loose Coupling</b>: Loose coupling is an attribute of systems, referring to an approach to designing interfaces across modules to reduce the interdependencies across modules or components – in particular, reducing the risk that changes within one module will create unanticipated changes within other modules. This approach specifically seeks to increase flexibility in adding modules, replacing modules and changing operations within individual modules.
In a loosely coupled exchange, the two participants may have specific, but more limited knowledge about each other. Such information appears in a Service contract, which is a document external to each participant that provides the information each participant needs to interact with the other.
Warm Regards,
Subhasha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.