Unwired Platform Runtime can be implemented as a clustered or non-clustered system. Clustering creates redundant Unwired Platform components on your network to provide a highly scalable and available system architecture.
A non-clustered Unwired Platform Runtime system is simpler, less expensive to deploy, and generally easier to maintain. However, a non-clustered system has significant limitations:
- It cannot take advantage of conventional load-balancing and failover mechanisms to provide higher system availability.
- The only sure way to increase overall system performance is to upgrade the host system resources (CPU, RAM, etc.).
A clustered system design helps to meet requirements for scalability, higher availability, and overall higher system performance
There are two main advantages of a clustered Unwired Platform system:
- Redundant cluster nodes allow conventional load-balancing and failover
mechanisms to provide higher system availability.
- For Online Data Proxy, and Unwired Platform implementations that deploy online
HTML5/JS hybrid apps (specifically those that use an online MBO cache policy),
the runtime environment can be scaled by adding or subtracting servers (nodes in
a cluster), to adapt to changes in system load or performance requirements.
For additional information see:
- Deployment Planning in Installation Guide for Runtime
- Cluster Administration Overview in
System Administration
- Administer: Clusters in Sybase Control Center for Sybase Unwired Platform or
in Sybase Control Center for Online Data Proxy