Single Node Deployment

You can deploy the WSO2 Integrator: SI as a single node deployment to achieve most of the use cases that commonly arise in the streaming integration world. The other deployment options, namely Minimum High Availability (HA) Deployment and Scalable High Available(HA) Deployment are mainly introduced to handle high availability, scalability, and resiliency. However, single node deployment too allows you to achieve resilient deployment as explained in the Resilient Deployment subsection.

System Requirements

For system requirements for this deployment, see Installing the WSO2 Integrator: SI in a Virtual Machine.

Resilient deployment

Resiliency guarantees the ability to withstand or recover from any system failure and carry out the process without loosing any data. WSO2 Integrator: SI has the capability to achieve the above via a broker that can replay data from a certain checkpoint. Kafka is one such broker that you can configure with WSO2 Integrator: SI to achieve this. The only additional configuration that you need to do in WSO2 Integrator: SI is state persistence. For detailed instructions, see Configuring Database and File System State Persistence.

If the single WSO2 Integrator: SI node fails to receive incoming events and if you have configured state persistence, the single node is able to retrieve the latest snapshot from the database and request the broker to send the events that it was unable to process due to the failure

The only disadvantage of this approach is that you need to ensure that there is a reliable mechanism to restart the server once it fails.