Loose Coupling
A communication intermediary separates application functionality from concerns of communication partners regarding their location, implementation platform, the time of communication, and the used data format.
 |
How can dependencies between Distributed Applications and between individual components of these applications be reduced? |
Context
Information exchange between applications and their individual components as well as associated management tasks, such as scaling, failure handling, or update management can be simplified significantly if application components can be treated individually and the dependencies among them are kept to a minimum.
Solution
Communicating components and multiple integrated applications are decoupled from each other by interacting through a broker. This broker encapsulates the assumptions that communication partners would otherwise have to make about one other and, thus, ensures separation of concerns.
Related Patterns
Distributed Application, Two-Tier Cloud Application, Hypervisor, Eventual Consistency, Message-oriented MiddlewareWatchdog