Message Broker - Enterprise Integration Patterns

Tags

Top Highlights

• in aggregate

• Many patterns

• route messages to the proper destination without the originating application being aware of the ultimate destination of the message

• can receive messages from multiple destinations

• determine the correct destination

• hub-and-spoke architectural style

• route the message to the correct channel

• As such

• concerns itself with larger solutions and helps us deal with the inevitable complexity of managing such a system

• is not a monolithic component

• once you decide to use the Message Broker as an architectural pattern

• you can choose the correct Message Router design patterns to implement the Message Broker

• disadvantage

• bottleneck

• alleviate

• stateless

• throughput

• Point-to-Point Channel

• ensure that only one instance of the Message Broker consumes any incoming message

• über-Message Broker