The recommended deployment for WSO2 Stream Processor is the Minimum HA Deploment. However, that deployment pattern involves using only two nodes and it is not scalable beyond that. If you want to configure WSO2 Stream Processor as a scalable deployment, you can use the Active-Active deployment pattern. For an overview of the Active-Active deployment pattern and instructions to configure it, see the following topics.
| Table of Contents | ||||
|---|---|---|---|---|
|
Overview
The above diagram represents a deployment where you are not limited to two nodes. You can scale the event processing horizontally by adding more Stream Processor Worker nodes to the deployment. In this deployment, it is recommended to configure the client appl to publish events to multiple SP worker nodes in a Round Robin manner to ensure better fault tolerance. The publishing of events can be carried out by one or more clients.
...
Now let's assume that the following input events were generated for the two nodes during a specific hour.
Node 1
| Event | symbol | price | quantity |
|---|---|---|---|
1 | wso2 | 100 | 10 |
| 2 | wso2 | 100 | 20 |
Node 2
| Event | symbol | price | quantity |
|---|---|---|---|
| 1 | wso2 | 100 | 10 |
| 2 | wso2 | 100 | 30 |
Here, node 1 calculates an hourly total of 30, and node 2 calculates an hourly total of 40. When you retrieve the total for this hour via a retrieval query, the result is 70.
...