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:
“I am the very pattern of a modern Major-Gineral,
I’ve information vegetable, animal, and mineral;
I know the kings of England, and I quote the fights historical,
From Marathon to Waterloo, in order categorical;”
—Sir William Schwenck Gilbert (1836–1911)
“Man is eminently a storyteller. His search for a purpose, a cause, an ideal, a mission and the like is largely a search for a plot and a pattern in the development of his life story—a story that is basically without meaning or pattern.”
—Eric Hoffer (1902–1983)
“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)