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:
“The kind of relatedness to the world may be noble or trivial, but even being related to the basest kind of pattern is immensely preferable to being alone.”
—Erich Fromm (1900–1980)
“In this lucid and flexible pattern only one thing remained always stationary, but this fallacy went unnoticed by Martha. The blind spot was the victim. The victim showed no signs of life before being deprived of it. If anything, the corpse which had to be moved and handled before burial seemed more active than its biological predecessor.”
—Vladimir Nabokov (1899–1977)
“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)