Pattern
A message broker is an architectural pattern for message validation, message transformation and message routing. It mediates communication amongst applications, minimizing the mutual awareness that applications should have of each other in order to be able to exchange messages, effectively implementing decoupling.
The purpose of a broker is to take incoming messages from applications and perform some action on them. The following are examples of actions that might be taken in the broker:
- Route messages to one or more of many destinations
- Transform messages to an alternative representation
- Perform message aggregation, decomposing messages into multiple messages and sending them to their destination, then recomposing the responses into one message to return to the user
- Interact with an external repository to augment a message or store it
- Invoke Web services to retrieve data
- Respond to events or errors
- Provide content and topic-based message routing using the publish/subscribe model
Read more about this topic: Message Broker
Famous quotes containing the word pattern:
“We took advantage of [the Indians’] ignorance and inexperience to incline them the more easily toward treachery, lewdness, avarice, and every sort of inhumanity and cruelty, after the example and pattern of our ways.”
—Michel de Montaigne (1533–1592)
“Our national experience in Americanizing millions of Europeans whose chief wish was to become Americans has been a heady wine which has made us believe, as perhaps no nation before us has ever believed, that, given the slimmest chance, all peoples will pattern themselves upon our model.”
—Ruth Benedict (1887–1948)
“Each child is an adventure into a better life—an opportunity to change the old pattern and make it new.”
—Hubert H. Humphrey (1911–1978)