This documentation is for WSO2 Private PaaS 4.0.0. View documentation for the latest release.
Private PaaS Communication - WSO2 Private PaaS 4.0.0 - WSO2 Documentation
||
Skip to end of metadata
Go to start of metadata

WSO2 Private Paa has a unified communication. A Message Bus is used to communicate between the components in WSO2 Private Paa; while, a Real-time Event Bus is used to handle the complex processors in WSO2 Private PaaS.  

WSO2 Private PaaS currently uses Apache ActiveMQ as its Message Bus. However, WSO2 Private PaaS supports any Message Bus (e.g., WSO2 Message BrokerRabbitMQ, and more) that supports the AMQP messaging technology. The Message Bus uses the AMQP protocol to handle all its communication.

In addition, WSO2 Private PaaS uses WSO2 Complex Event Processor as the Real-time Event Bus and uses the Thrift protocol to communicate with the components. The messages sent to the Real-time Event Bus from the Health Publisher will contain the following name value pairs, which have a predefined format based on the Thrift protocol: Cluster ID, Network partition ID, Member ID, Partition ID, Health Description and Value.

As Message Broker uses the standard pub/sub mechanism for communication, it allows anyone to write their own extensions using this mechanism to extend Private PaaS into their own environment. For example, if someone needs to write a monitoring application, they can subscribe to the Topology topic and draw a topology diagram within the respective service cluster in order to update the dashboard using the given information. 

  • No labels