Broker pattern

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 220.237.33.182 (talk) at 22:00, 28 November 2012 (Fixed typos/errors (responlble -> responsible, wlth -> with, Is -> is, '.' -> ',')). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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.