WSO2 Carbon version 4.0.0 onwards supports deployment models that consist of 'worker' nodes and 'manager' nodes. A worker node serves requests received by clients, whereas a manager node deploys and configures artifacts (web applications, services, proxy services, etc.).
This The worker/manager deployment setup provides proper separation of concerns between setup separates a WSO2 product's UI components, management console, and related functionality with its internal framework that serves requests to deployment artifacts. Typically. Typically, the management manager nodes are in read-write mode and authorized to make configuration changes. The worker nodes are in read-only mode and authorized only to deploy artifacts and read configurations. This deployment model provides improved security as you can set up the manager nodes behind an internal firewall, exposed only to internal clients, while the worker nodes are exposed externally. Also, since the user interface is not loaded into 'worker' nodes, this deployment model is more efficient in utilizing memory.
Why separate the worker and manager nodes
...
- Improved security: Manager nodes are typically behind a firewall that only allows admin access. They are exposed to clients running within the organization only, while worker nodes can be exposed to external clients.
- Proper separation of concerns: Management nodes specialize in the management of the setup while worker nodes specialize in serving requests to deployment artifacts. Only management nodes are authorized to add new artifacts into the system or make configuration changes.
- Specific worker-node tasks: Worker nodes can only deploy artifacts and read configuration. The separation enables you to have worker nodes Worker nodes are limited only for specific tasks.
- Lower memory requirements: There is a lower memory footprint in the worker nodes because the OSGi bundles related to the management console and UI are not loaded to them. This is also good for performance.
Worker/Manager separated clustering patterns
Since all WSO2 products are built on the cluster-enabled Carbon platform, you can cluster most WSO2 products in the same way, depending on which deployment pattern you use. The process of separating the worker and manager nodes depends on the worker/manager clustering pattern you choose. You can select one of the following patterns based on your load and the targeted expenditure.
| Note |
|---|
Your configuration changes depending on which clustering deployment pattern you choose. Although we use WSO2 API Manager (APIM) in the examples, the concepts apply equally to other WSO2 products as well. |
...
This pattern has two manager nodes in one sub-domain and two worker nodes in a separate sub-domain. The manager and worker sub-domains are part of a single WSO2 product cluster domain. Both sub-domains use their own load balancer while existing within the same cluster. Multiple load balancers result in several unique configuration steps, so please ensure that you follow the relevant steps carefully. This pattern is similar to deployment pattern 2. However, the application/modification load (or any other administrative load) might be high, so there is a dedicated load balancer for the manager cluster to prevent this load from affecting the load of the worker cluster.
