This documentation is for older WSO2 products. View documentation for the latest release.
Clustering Message Broker - Clustering Guide 4.2.0 - WSO2 Documentation
Skip to end of metadata
Go to start of metadata

By default, WSO2 Message Broker is packaged with all three of the following components:

  • Broker
  • Cassandra Server
  • ZooKeeper Server

In a clustered setup, it is possible to have these three components separately and shared with each other. This separation introduces several possible deployment scenarios that can be customized according to your requirement. However, this deployment can be done with just WSO2 MB alone as illustrated in Clustering MB Using Profiles.

Although we have explained four other clustering deployment scenarios for MB, we highly recommend the scenario in this topic (Clustering MB using profiles) for production environments.

To enable the WSO2 Governance Registry to be used across all nodes, you must share the registry. For details, see Sharing the Governance Registry Across the MB Cluster.

Advantages of WSO2 Message Broker

Message Broker can be scaled up to meet high messaging demands. The advantages that can be gained by clustering the Message Broker are listed below.

  1. Scalability is useful as adding more Message Broker nodes to your cluster enables you to publish your messages or do subscriptions in a load balanced way.
  2. Cassandra can be scaled for high availability and high speed message writing and reading.
  3. Cassandra is very fast in reading and writing large messages natively, so this is ideal in a clustered environment.

Due to the above reasons, WSO2 Message Broker can deliver high performance results as opposed to many commercial and conventional Message Brokers that have very low performance when "size of a message" becomes too large. If you are unhappy with the performance, it can be scaled to meet your requirements.


  • No labels