Deployment Patterns
- Former user (Deleted)
WSO2 Private PaaS 4.0.0 supports two methods in deploying the provided WSO2 AS, WSO2 BPS and WSO2 ESB cartridges as described below. For the deployment of these WSO2 cartridges, you can select one of the following patterns based on your load coupled with your targeted expenditure:
Deploying as a clustered service
This is the deployment pattern that is used by default for all the provided WSO2 Cartridges. For more information on deploying as a clustered service, see Clustering.
If you provide the information in the product configuration as such that, you do not need to deploy the WSO2 product in worker/manager setup, then the cartridges will be deployed as a clustered service. Otherwise, the worker manager deployment pattern will be used.
Worker/manager deployment pattern
Worker/manager deployment model consists of 'worker' nodes and 'management' nodes. A worker node is used to serve requests received by clients, whereas a management node is used to deploy and configure artifacts (web applications, services, proxy services, etc.).
This worker/manager deployment setup provides proper separation of concerns between the Private PaaS UI components, management console, and related functionality with its internal framework serving requests to deployment artifacts. Typically, the management nodes are in read-write mode and authorized to add new artifacts or make configuration changes, whereas the worker nodes are in read-only mode, authorized only to deploy artifacts and read configurations. This deployment model provides improved security, since its management nodes can be set up behind an internal firewall and only exposed to internal clients while only worker nodes can be exposed externally. Also, since the user interface is not loaded onto 'worker' nodes, the deployment model is more efficient in memory utilization.
The minimum setup of the worker/manager deployment model with one manager and two workers, is illustrated in the figure below:
