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:
“In almost every marriage there is a selfish and an unselfish partner. A pattern is set up and soon becomes inflexible, of one person always making the demands and one person always giving way.”
—Iris Murdoch (b. 1919)
“The worthiest man to be known, and for a pattern to be presented to the world, he is the man of whom we have most certain knowledge. He hath been declared and enlightened by the most clear-seeing men that ever were; the testimonies we have of him are in faithfulness and sufficiency most admirable.”
—Michel de Montaigne (1533–1592)
“It is just possible that the tensions in a novel of murder are the simplest and yet most complete pattern of the tensions on which we live in this generation.”
—Raymond Chandler (1888–1959)