Skip to Content
avatar image
Former Member

what is loose and tight coupling.

what is loose and tight coupling.give me description about that.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Dec 13, 2006 at 06:39 AM

    How about this site as first step?

    http://en.wikipedia.org/wiki/Loose_coupling

    Regarding SAP related, this forum would help you.

    Loosely coupled systems

    Best Regards.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 22, 2006 at 09:28 AM

    Hi Chiru,

    Consider a simple scenario where an application / service / entity wants to "call" another application / service / entity by passing some request parameters (and getting some response back typically).

    The <b>loose coupling</b> means, the calling entity needs to pass only the request parameters correctly to the second entity, <b>without worrying about the internal implementation</b> of that entity. So as long as request and response structure of second entity remains same, it can be called or "consumed" any no. of times as desired.

    In case of <b>tight coupling</b>, the implementation in first entity depends on the implementation in the second entity. So if second entity's code changes, the first one also has to modify its code accordingly. This puts rework and is less efficient.

    Regards,

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 02, 2007 at 07:11 AM

    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

    Add comment
    10|10000 characters needed characters exceeded