Clustering Overview

Individual WebApp Secure appliances have the ability to work together as one system in a cluster. Clustering allows traffic to be divided among multiple appliances, effectively reducing the per-system load. In a clustered network configuration, the master node holds the database that is populated by one or more traffic processors" In order to successfully utilize a WebApp Secure cluster, a load-balancer must properly segregate traffic to each of the defined traffic processing nodes. Each of these traffic nodes must maintain connectivity with the master in order to operate.

Note: Clustering should not be confused with High Availability. Clustering is used to increase throughput (by utilizing multiple processing nodes), and can reduce the chance that the whole system will fail. Clustering does not protect the master node from failure as in a High Availability setup; only HA configurations are set up to include failsafe procedures to designate a new master when the first one is unavailable.

In a traditional WebApp Secure deployment (one system), the appliance is responsible for holding its own database as well as processing the traffic. In a clustered deployment, you have the ability to segregate the database from those systems which will process incoming requests. During cluster configuration, you will have the ability to designate a node type for each system. At a minimum, the cluster must have a way to process traffic and a way to store the relevant information.

Node types are as follows: