Top Menu

Cluster/Protocol is the name of the service as seen on the order form and in the account billing.

Note that typically clients may start with only 1-2 clusters/protocols with 2 or more servers; however, it is also possible to set-up multiple separate clusters within 2 or more servers (generally servers are added in increments of 2 however can add 1 at a time)

Total Included Connections is the number of instantaneous connections included. If one cluster is set-up, the total connections are set-up as the limit for the cluster as a whole (or alternatively, at customer's choice, per each individual server). If multiple clusters are set-up, then the distribution of connections per cluster is done as per customer instructions.

NOTE: Adding an additional server for regular (non-HTTPs) server load balancing will add another 1000 connections; adding an additional service instance for the HTTPs server load balancing services will add another 750 connections.

A Server/Port is defined as an IP:port combination. Keep in mind that the load balancing is done per port/protocol, and not per server as a whole. As such, if only 1 protocol (e.g. HTTP, port 80) is load balanced on a group of servers, then each server will only need 1 protocol/cluster per server. If, however, 3 protocols (e.g. HTTP, port 80; FTP, port 21, and POP3, port 110) are to be balanced on the same group of servers, then each server will need to have 3 protocols added, and there will be three separate clusters, one for each protocol.

It is very simple, start with our initial 2 server load balancing solution (either regular or HTTPs, depending on whether you need HTTPs) which includes 2 servers with 1 protocol/cluster then add additional servers and protocols as suits your needs. Typically only the customer-facing mission critical services are load balanced (most commonly HTTP and HTTPS); back-end services only used for maintaining the sites, such as FTP, are not normally load balanced.