Loose coupling

Loose coupling in broader distributed system design is achieved by the use of transactions, queues provided by message-oriented middleware, and interoperability standards.

They are different in that RPC- and ORB-based middleware create systems of tightly coupled components, whereas MOM-based systems allow for a looser coupling of components.

The related buzzword service-orientation promotes loose coupling between services.

Loose coupling in broader distributed system design is achieved by the use of transactions, queues provided by message-oriented middleware, and interoperability standards.

Distributed programming typically falls into one of several basic architectures: client–server, three-tier, n-tier, or peer-to-peer; or categories: loose coupling, or tight coupling.

Event-driven architecture also aims at promoting loose coupling.

This architectural pattern may be applied by the design and implementation of applications and systems that transmit events among loosely coupled software components and services.

Subareas include the coupling of classes, interfaces, data, and services.

Low coupling often correlates with high cohesion, and vice versa.

In its general form, the LoD is a specific case of loose coupling.

High cohesion often correlates with loose coupling, and vice versa.

In computing and systems design a loosely coupled system is one in which each of its components has, or makes use of, little or no knowledge of the definitions of other separate components.

In computing and systems design a loosely coupled system is one in which each of its components has, or makes use of, little or no knowledge of the definitions of other separate components.

In computing and systems design a loosely coupled system is one in which each of its components has, or makes use of, little or no knowledge of the definitions of other separate components.

Data replication across different systems provides loose coupling (in availability), but creates issues in maintaining consistency (data synchronization).

Data replication across different systems provides loose coupling (in availability), but creates issues in maintaining consistency (data synchronization).

Data replication across different systems provides loose coupling (in availability), but creates issues in maintaining consistency (data synchronization).

Loose coupling of interfaces can be enhanced by publishing data in a standard format (such as XML or JSON).

Loose coupling of interfaces can be enhanced by publishing data in a standard format (such as XML or JSON).

Loose coupling in computing is interpreted as encapsulation vs. non-encapsulation.

This is a UML diagram illustrating an example of loose coupling between a dependent class and a set of concrete classes, which provide the required behavior:

Computer programming languages having notions of either functions as the core module (see Functional programming) or functions as objects provide excellent examples of loosely coupled programming.

Functional languages have patterns of Continuations, Closure, or generators.

Functional languages have patterns of Continuations, Closure, or generators.

See Clojure and Lisp as examples of function programming languages.

See Clojure and Lisp as examples of function programming languages.