Broker architectural pattern in plain english

habitats picture habitats · May 23, 2014 · Viewed 12.6k times · Source

Could someone explain the Broker pattern to me in plain english? Possibly in terms of Java or a real life analogy.

Answer

Adam Yost picture Adam Yost · May 23, 2014

Try to imagine that 10 people have messages they need to deliver. Another 10 people are expecting messages from the previous group. In an open environment, each person in the first group would have to deliver their message to the recipient manually, so each person has to visit at least one member of the second group. This is inefficient and chaotic.

In broker, there is a control class (in this case the postman) who receives all the messages from group one. The broker then organizes the messages based off destination and does any operations needed, before visiting each recipient once to deliver all messages for them. This is far more efficient.

In software design, this lets remote and heterogeneous classes communicate with each other easily. The control class has an interface which all incoming messages can interact with so a sorts of messages can be sent and interpreted correctly. Keep in mind this is not very scalable, so it loses effectiveness for larger systems.

Hope this helped!