In a production environment, WSO2 Message Broker can be clustered and configured with an external Database Management System (DBMS) of your choice.
Deployment architecture
The following is the common deployment model referred to in the configurations. This is the recommended deployment pattern for WSO2 Message Broker and depicts the minimum number of broker nodes necessary to achieve high availability and high efficiency in the cluster.
Figure 1: Message Broker Nodes Configured With An External DBMS Cluster.
In this deployment model, assume that all these nodes are on different hosts. There are two WSO2 Message Broker nodes and any number of nodes that you prefer for the external DBMS (this can even be a single node).
| Server | IP Address |
|---|---|
| MB Server 01 | 192.168.0.102 |
| MB Server 02 | 192.168.0.103 |
| DBMS 01 | 192.168.0.104 |
| DBMS 02 | 192.168.0.105 |
| DBMS 03 | 192.168.0.106 |
| DBMS 04 | 192.168.0.107 |
Although this example specifies two WSO2 Message Broker nodes as a minimum requirement for optimal performance, you can have more Message Broker nodes depending on your requirement.
Follow the instructions below to configure the cluster.
Configuring WSO2 Message Broker
Use the instructions available in the following sections to configure the two Message Broker nodes and connect them to an external DBMS.
Advantages of WSO2 Message Broker
The advantage that can be gained when clustering the Message Broker is that you can have a very scalable product. This 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. The Message Broker can also be scaled up to meet high messaging demands and if you are unhappy with the performance, MB can be scaled to meet your requirements.
Due to the above reason, WSO2 Message Broker can deliver high performance results as opposed to many commercial and conventional Message Brokers that have very low performance when the "size of a message" becomes too large.