SYNC Communication Platform “Message Broker Based”

INTRODUCTION
In a telecommunication network where programs communicate by exchanging formally-defined messages (that is, through the act of messaging ), a message broker is an intermediary program that translates messages from the formal messaging protocol of the publisher to the formal messaging protocol of the receiver. Message broker programs are sometimes known as middleware.
How applications communicate is becoming an increasingly large challenge. Using Messaging Middleware simplifies this challenge and allows for common communications infrastructure that grows and scales to meet the most demanding conditions. But communication can happen in many different forms and how Messaging Middleware provides communication is no different.
With a Message Broker, the source application (producer) sends a message to a server process that can provide data marshaling, routing, message translation, persistence and delivery to all the appropriate destinations (consumers). The defining characteristic of a Message Broker is that the broker itself is a discrete service. Producers and consumers communicate with the broker using standard or proprietary protocols. The Message Broker typically provides all the state management and tracking of clients so that individual applications do not need to take on this responsibility and the complexity of message delivery is built into the Message Broker itself.
There are two basic forms of communications with a Message Broker:

• Publish and Subscribe (Topics)
• Point-to-Point (Queues)

FUNCIONALIDAD
There are numerous messaging patterns (such as publish / subscribe) that can operate without a messaging broker. A pattern that does require the intervention of a messaging broker is that of work queues, that is, messaging queues handled by multiple receivers. Such queues are required to have a single central management mechanism, transaction and generally also reliable storage.
ACTUALIDAD
List of message broker software

• Amazon Web Services (AWS) Simple Queue Service (SQS)
• Apache ActiveMQ
• Apache Kafka
• Apache Qpid
• Celery
• Cloverleaf (E-Novation Lifeline)
• Comverse Message Broker (Comverse Technology)
• Enduro/X Transactional Message Queue (TMQ)
• Financial Fusion Message Broker (Sybase)
• Fuse Message Broker (enterprise ActiveMQ)
• Gearman
• HornetQ (Red Hat)
• IBM App Connect
• IBM MQ
• JBoss Messaging (JBoss)
• JORAM
• Microsoft Azure Service Bus (Microsoft)
• Microsoft BizTalk Server (Microsoft)
• NATS (MIT Open Source License, written in Go)
• Open Message Queue
• Oracle Message Broker (Oracle Corporation)
• RabbitMQ (Mozilla Public License, written in Erlang)

RabbitMQ has the following advantages:
·        Fast
·        Polyglot
·        Simple management
·        No Erlang knowledge needed
·        Great documentation and community

• Redis An open source, in-memory data structure store, used as a database, cache and message broker.
• SAP PI (SAP AG)
• Solace PubSub+
• Spread Toolkit
• Tarantool, a NoSQL database, with a set of stored procedures for message queues
• TIBCO Enterprise Message Service
• WSO2 Message Broker