Feature | Description |
|---|
Elastically Scale Worker Nodes | - The WSO2 ELB monitors load on worker nodes and starts or terminates nodes based on need.
- Scaling comes by talking to underlying Infrastructure as a Service (IaaS).
- Scaling can happen across multiple underlying IaaS simultaneously.
|
IaaS-Independent Elasticity | - Auto-scaling components of the WSO2 ELB supports execution on top of various IaaS offerings including Amazon EC2, Eucalyptus, Ubuntu Cloud, Openstack and VMware.
- Multiple IaaS offerings can be registered at once via JClouds API.
|
Cloud Bursting to Hybrid Clouds | - Service clusters can have a static worker pool and an additional burst pool.
- Bursting can span across public and private clouds using different IaaS providers at the same time.
- Allows you to extend your data center’s processing capabilities by leveraging the computing power available on public clouds such as Amazon EC2.
|
Tenant-Aware Load Balancing | - Dynamic tenant loading and unloading after a defined time.
- Tenants can be partitioned to different service clusters.
|
"Private Jet" Mode for Tenants | Multi-tenant deployments can allow some tenants’ load to deploy in a single tenant mode. Clusters are isolated for special privileges such as priority processing, user-based customized actions and improved performance. Allocate entire service clusters by tenant, through the loadbalancer.conf file, ensuring that all requests to the tenant will be forwarded to a particular cluster.
|
| Service-Aware Load Balancing | - The WSO2 ELB can load balance multiple services at once.
- Services can be configured to different service clusters or shared service clusters.
|
| Dynamic Discovery | - WSO2 ELB dynamically discovers worker nodes.
- Adds or removes new nodes without restarting system.
- Adds or removes entire clusters dynamically.
- Notifies all load balancers when a new node is added to the cluster.
|
| Administrator-Friendly | - Simple, textual configuration language and configuration files with details.
- Fast startup times and dynamically-reconfigurable.
- Easy to manage and monitor with systems such as Nagios and Unix.
|
Data Partitioning | - Partitions data based on a given factor such as the geographic location.
For example, if tenants 1 to 100 should load and store data in the United States, a new application cluster can be deployed at the United States and informed to the Load Balancer. The loadbalancer.conf file can be configured to specify that tenants 1 to 100 are loaded at a particular cluster (named as wso2.as.usa.domain) ensuring that all requests coming to tenants 1 to 100 will be forwarded to that cluster and the data related to those tenants (e.g. application files, databases) will be stored in servers at the United States. |