This documentation is for WSO2 Message Broker version 2.0.1. View documentation for the latest release.

Clustered Deployment

Owned by Former user (Deleted)
Last updated: Nov 19, 2012Version comment
1 min read

Clustering capability in WSO2 MB facilitates high-availability and fail-over support. Several Message Broker nodes can be set up and configured to work as a cluster, so that when one node is down, message routing and handling will be taken over by other nodes in the cluster. At the same time, overhead of routing messages is distributed among the Message Broker cluster nodes so that overall performance of the Message Brokering is significantly better. As a result, the Message Broker can sustain a lot of publishers and subscribers and scale to suit new demands. There is no significant performance degradation with the number of publishers, subscribers and exchanges. Fault tolerance brings more benefits in deployment apart from the performance gains.

There are several cluster deployment models supported by WSO2 Message Broker. The section Clustered Deployment Patterns explains which clustering option is best-fit for your business use-case and how to configure it Â