Non-clustered Systems

In a non-clustered system, all Unwired Platform server components (the Unwired Server and data tier servers) are installed by a single installation procedure, on a single host.

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 be scaled by adding or subtracting servers, to adapt to changes in system load or performance requirements.
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.).

Note: You cannot upgrade a non-clustered Unwired Platform system to a clustered system. To replace a non-clustered system with a clustered system, you must redeploy the Unwired Platform system, using cluster installation options on suitable hosts.

When you choose between clustered and non-clustered designs, you must plan carefully. If you can reasonably foresee any future requirement for a clustered system, such as a service level agreement (SLA) that would require scalability, or higher system availability), you should consider deploying a clustered Unwired Platform system.