A Siddhi Application is a combination of multiple Siddhi executional elements. A Siddhi executional element can be a Siddhi Query or a Siddhi Partition. When defining a Siddhi application, you can specify a number of parallel instances to be created for each executional element, and how each executional element must be isolated for an SP instance. Based on this, the initial Siddhi application is divided into multiple Siddhi applications and deployed in different SP instances.
This deployment pattern is supported so that a high volume of data can be distributed among multiple SP instances instead of having them accumulated at a single point. Therefore, it is suitable to be used in scenarios where the volume of data handled is too high to be managed in a single SP instance.
Creating a distributed Siddhi application
This section explains how to write distributed Sidhi applications by assigning executional elements to different execution groups.
A distributed Siddhi application can contain one or more of the following elements:
Queries that only consider currently incoming events when generating an output.
|Stateful queries||Queries that consider both currently incoming events as well as past events when generating an output.|
e.g., windows, sequences, patterns, etc.
|Partitions||Collections of stream definitions and Siddhi queries separated from each other within a Siddhi application for the purpose of processing events in parallel and in isolation.|
The following annotations are used when writing a distributed Siddhi application.
All the executional elements with the same execution group are executed in the same Siddhi application. When different execution groups are mentioned within the same distributed Siddhi application, WSO2 SP initiates a separate Siddhi Application per execution group. In each separated Siddhi application, only the executional elements assigned to the relevant execution group are executed.
Executional elements that have no execution group assigned to them are executed in a separate SP instance.
The number of instances in which the executional element must be executed in parallel. All the executional elements assigned to a specific execution group (i.e., via the
When the number of parallel instances to be run is not given for the executional elements assigned to an execution group , only one Siddhi application is initiated for that execution group.
This can also be applied to sources. If a parallelism count is specified within a source annotation, a number of passthrough Siddhi applications equal to that count are generated and deployed.
The following is a sample distributed Siddhi application.
When above siddhi application is deployed it creates a distributed processing chain as depicted in the image below.
As annotated in the Siddhi application, two passthough query groups are created to accept HTTP traffic and to send those events into the messaging layer. Other execution groups are created as per the given parallelism count. The execution group creation is summarized in the table below.
Number of Siddhi