Broker pattern: Difference between revisions
Appearance
Content deleted Content added
CAPTAIN RAJU (talk | contribs) m Reverted 1 edit by 182.181.252.147 identified as test/vandalism using STiki |
Tags: Mobile edit Mobile web edit |
||
Line 10: | Line 10: | ||
* Inherent networking complexities such as security concerns, partial failures, etc. |
* Inherent networking complexities such as security concerns, partial failures, etc. |
||
* Networking diversity in protocols, operating systems, hardware. |
* Networking diversity in protocols, operating systems, hardware. |
||
Services for adding, removing |
|||
== Solution == |
== Solution == |
Revision as of 11:06, 14 December 2016
The Broker architectural pattern can be used to structure distributed software systems with decoupled components that interact by remote service invocations. A broker component is responsible for coordinating communication, such as forwarding requests, as well as for transmitting results and exceptions.
Context
- A system that consists of multiple remote objects which interact synchronously or asynchronously.
- Heterogeneous environment.
Problems
- Usually, there is a need of having great flexibility, maintainability and changeability when developing applications.
- Scalability is reduced.
- Inherent networking complexities such as security concerns, partial failures, etc.
- Networking diversity in protocols, operating systems, hardware.
Services for adding, removing
Solution
Separate system communication functionality from the main application functionality by providing a broker that isolates communication-related concerns.