SlideShare a Scribd company logo
Broker PatternBackbone of DistributedProcessing
Name: NilayMishra
Objective:
To understand the broker pattern, its advantage and the usage of pattern in distributed computing.
Where it can be applied and case study.
Broker Design Pattern
Broker design patter can be used to architecture distributed software systems and decouple components that
interact via remote service invocation or RMI over the internet. As the world suggests, broker pattern works as
mediator which connects two different parties and establish communication b/w them without exposing their
identity to each other’s.
Broker pattern is also worked as a messaging server which transfers messaged b/w different systems.
Real Life Example: A real-time example of broker in our daily life is like any online shopping sites which works
as mediator like Amazon, Flipkart, Myntra, and Alibaba etc. which works as a broker, these sites connects
multiple sellers to millions of buyers or the property broker which connects property owners to buyers or sellers.
Technical Example: Broker pattern is largely used in middleware technologies as messaging servers which
takes responsibility of transferring messages b/w two different systems E.g. Java Messaging Server (JMS) is
the most popular and commonly used open standard messaging facility provided by sun microsystem which is
built on top of broker design pattern.
Other middleware technologies which implement broker pattern with their own ways are: Software AG
Broker, TIBCO, and Mule Soft Universal Messaging Software which connects two heterogeneous systems.
Typesof Communication Provided by Broker Patten
1- Point to Point Communication- one party wants to send a message to the only single receiver.
2- Publisher and Subscriber- one party wants to send a message to 1 or more subscribers.
Case Study
Domain: Online Order Management System
Reference: Motorola Mobility Inc.
Problem: Details of an online order of Motorola mobiles are supposed to send to multiple systems which are
geographically separated.
Description: Consider an online shopping system when you plan an online order corresponding order details
are supposed to send to multiple systems in order to fulfil your order E.g. Financial System, Fulfilment System,
Demand and order Management System, Logistic System, Inventory Management etc.
All the system is expecting the same set of data and wants to process it their own business logic. In this
types of approach to write a separate set of code and do tight coupling of resources is not economic solution,
we can implement this by writing the n number of packages for n different systems but this will hamper the
performance very badly and in future change in one system lead to the change in current running code. This
significantly increases the complexity of the system.
Solution: Implement a broker pattern by using any of the software provided in the market or write your own
java code which published messages to Queues and registers multiple subscribers for that Queues.
1- Each Subscriber will be having a unique ID and subscriber to particular Queues and type of messages
2- Subscriber can only receive the message for which they are subscribed to.
3- If a new subscriber wants to subscribe/unsubscribe the queue then he can be done at runtime.
Available Software’s: SAG Broker, SAG Universal Messaging, Oracle SOA Environment, TIBCO, Mule Soft,
JMS,
Used Technology: SAG Broker- Software AG Broker,
Implementation Product- Moto-G mobile family implemented for the order fulfilment in the US via
www.motomaker.com to Demand ware system integration.
Implementation Diagram
In thisDiagramif you can see one systemMortgage isa producerwhichsendsmessagestotarget
systems.Thismortgage isa frontendapplicationwhichtakesuserorderandcreateda canonical
documentwhichispublishedtomultiple endsystem.

More Related Content

PPT
Distributed Systems
PDF
Maq Software Live On Cutting Edge Dream Spark Yatra
PPTX
Broker: adventure through architecture pattern
DOC
Unit 1 architecture of distributed systems
DOC
Java project titles
PPTX
UNIT 1 IOT ENABLING TECHNOLOGIES unit .pptx
DOCX
RabbitMQ in Microservice Architecture.docx
Distributed Systems
Maq Software Live On Cutting Edge Dream Spark Yatra
Broker: adventure through architecture pattern
Unit 1 architecture of distributed systems
Java project titles
UNIT 1 IOT ENABLING TECHNOLOGIES unit .pptx
RabbitMQ in Microservice Architecture.docx

Similar to Broker Pattern Backbone of Distributed Processing (20)

PPTX
SFDC Training Day 1SFDC Training Day 1.pptx
PDF
Mattermost vs riot matrix who is winning as an open-source slack alternative_
DOCX
DOTNET 2013 IEEE MOBILECOMPUTING PROJECT Privacy preserving distributed profi...
DOCX
Privacy preserving distributed profile matching in proximity-based mobile soc...
DOCX
JAVA 2013 IEEE MOBILECOMPUTING PROJECT Privacy preserving distributed profile...
PDF
MCP vs A2A vs ACP: Choosing the Right Protocol | Bluebash
DOC
Mobile agents in a distributed multimedia dabase system(synopsis)
PPTX
Introduction of Distributed Systems - Communication
PDF
An E-Business Integration And Collaboration Platform For B2B E-Commerce
PDF
Web Based Investment Management System
DOCX
Microsoft BizTalk server seen by the programmer’s eyes
PPTX
Machine learning presentation in using pyhton
PDF
A Practical Guide for Selecting an Enterprise Messaging Platforms
PDF
20CS503PE - Distributed systems Introduction.pdf
DOC
The Mobile Ecosystem Sumotext
PDF
e-commerce systems and infrastructure.pdf
PDF
How io t is changing our world
PDF
Tamer_Mohamed
PDF
How secure is the cloud? and Amazon vs Walmart which giant will dominant?
PPTX
Unit5-Cloud.pptx for lpu course cse121 o
SFDC Training Day 1SFDC Training Day 1.pptx
Mattermost vs riot matrix who is winning as an open-source slack alternative_
DOTNET 2013 IEEE MOBILECOMPUTING PROJECT Privacy preserving distributed profi...
Privacy preserving distributed profile matching in proximity-based mobile soc...
JAVA 2013 IEEE MOBILECOMPUTING PROJECT Privacy preserving distributed profile...
MCP vs A2A vs ACP: Choosing the Right Protocol | Bluebash
Mobile agents in a distributed multimedia dabase system(synopsis)
Introduction of Distributed Systems - Communication
An E-Business Integration And Collaboration Platform For B2B E-Commerce
Web Based Investment Management System
Microsoft BizTalk server seen by the programmer’s eyes
Machine learning presentation in using pyhton
A Practical Guide for Selecting an Enterprise Messaging Platforms
20CS503PE - Distributed systems Introduction.pdf
The Mobile Ecosystem Sumotext
e-commerce systems and infrastructure.pdf
How io t is changing our world
Tamer_Mohamed
How secure is the cloud? and Amazon vs Walmart which giant will dominant?
Unit5-Cloud.pptx for lpu course cse121 o
Ad

Broker Pattern Backbone of Distributed Processing

  • 1. Broker PatternBackbone of DistributedProcessing Name: NilayMishra Objective: To understand the broker pattern, its advantage and the usage of pattern in distributed computing. Where it can be applied and case study. Broker Design Pattern Broker design patter can be used to architecture distributed software systems and decouple components that interact via remote service invocation or RMI over the internet. As the world suggests, broker pattern works as mediator which connects two different parties and establish communication b/w them without exposing their identity to each other’s. Broker pattern is also worked as a messaging server which transfers messaged b/w different systems. Real Life Example: A real-time example of broker in our daily life is like any online shopping sites which works as mediator like Amazon, Flipkart, Myntra, and Alibaba etc. which works as a broker, these sites connects multiple sellers to millions of buyers or the property broker which connects property owners to buyers or sellers. Technical Example: Broker pattern is largely used in middleware technologies as messaging servers which takes responsibility of transferring messages b/w two different systems E.g. Java Messaging Server (JMS) is the most popular and commonly used open standard messaging facility provided by sun microsystem which is built on top of broker design pattern. Other middleware technologies which implement broker pattern with their own ways are: Software AG Broker, TIBCO, and Mule Soft Universal Messaging Software which connects two heterogeneous systems. Typesof Communication Provided by Broker Patten 1- Point to Point Communication- one party wants to send a message to the only single receiver. 2- Publisher and Subscriber- one party wants to send a message to 1 or more subscribers. Case Study Domain: Online Order Management System Reference: Motorola Mobility Inc. Problem: Details of an online order of Motorola mobiles are supposed to send to multiple systems which are geographically separated.
  • 2. Description: Consider an online shopping system when you plan an online order corresponding order details are supposed to send to multiple systems in order to fulfil your order E.g. Financial System, Fulfilment System, Demand and order Management System, Logistic System, Inventory Management etc. All the system is expecting the same set of data and wants to process it their own business logic. In this types of approach to write a separate set of code and do tight coupling of resources is not economic solution, we can implement this by writing the n number of packages for n different systems but this will hamper the performance very badly and in future change in one system lead to the change in current running code. This significantly increases the complexity of the system. Solution: Implement a broker pattern by using any of the software provided in the market or write your own java code which published messages to Queues and registers multiple subscribers for that Queues. 1- Each Subscriber will be having a unique ID and subscriber to particular Queues and type of messages 2- Subscriber can only receive the message for which they are subscribed to. 3- If a new subscriber wants to subscribe/unsubscribe the queue then he can be done at runtime. Available Software’s: SAG Broker, SAG Universal Messaging, Oracle SOA Environment, TIBCO, Mule Soft, JMS, Used Technology: SAG Broker- Software AG Broker, Implementation Product- Moto-G mobile family implemented for the order fulfilment in the US via www.motomaker.com to Demand ware system integration. Implementation Diagram In thisDiagramif you can see one systemMortgage isa producerwhichsendsmessagestotarget systems.Thismortgage isa frontendapplicationwhichtakesuserorderandcreateda canonical documentwhichispublishedtomultiple endsystem.