Load Balancing

Load Balancing Service

Load Balancing distributes traffic loads, processing and communications evenly across multiple servers within a data center so that a single device does not get overwhelmed. Load Balancing is essential in situations where it is difficult to predict the number of requests issued to a server, and can distribute requests that would have been made to a single server to ease the load and minimize latency and other issues. ZebraHost Load Balancing solutions enable customers to employ a variety of balancing methods to distribute traffic, including persistent and non-persistent options, that can be changed, activated and deactivated at any time.

Local, global, and high availability options can be activated, changed, and deactivated at any time and if you have questions about which load balancing solution is a best fit for your application, please contact us.

LOAD BALANCE METHOD	DESCRIPTION
Consistent Hash IP	Maps client requests to real servers by hashing the source IPs of the request. Client/Server relationships are maintained across ports.
Insert Cookie	Inserts a tracking cookie into the request. Session data contained within the cookie is used with subsequent request to send traffic back to the same real server. Persistence is hard-coded on a per-session basis. Cookie expires after the client's browser is closed. Requires that the client accepts cookies to be effective.
Least Connections	The real server with the fewest number of active connections gets first priority. Algorithm requires a difference of 10 connections, which may skew results for customers.
Persistent IP	Ties the source IP of the requester to the real server that processes the request by a hash of all 4 octets of the requesting IP address. Persists for 60 minutes.
Round Robin	Each New Request is assigned to the next real server in the rotation Balanced distribution occurs over large samples, though small samples may display a disproportionate balance.
Shortest Response	Server with the shortest response time receives the request. As load and response time increases, slower servers begin to field fewer requests.
Round Robin with Persistent IP	Each new request is assigned to the next real server in rotation. Requester's IP address is tied to the real server, resulting in subsequent requests from the IP to be assigned to the same real server.
Round Robin with Insert Cookie	Each new request is assigned to the next real server in rotation. The load balancer inserts a cookie into the request and uses the session information from the cookie to direct traffic to the same real server for subsequent requests.
Least Connections with Persistent IP	Each new request is assigned to the real server with the least number of active connections at the moment. Requester's IP address is tied to the real server, resulting in subsequent requests from the IP to be assigned to the same real server.
Least Connections with Insert Cookie	Each new request is assigned to the real server with the least number of active connections at the moment. The Load Balancer inserts a cookie into the request and uses the session information from the cookie to direct traffic to the same real server for subsequent requests.
Shortest Response with Persistent IP	Each new request is assigned to the real server with the shortest response time. Requester's IP address is tied to the real server, resulting in subsequent requests from the IP to be assigned to the same real server.
Shortest Response with Insert Cookie	Each new request is assigned to the real server with the shortest response time. The load balancer inserts a cookie into the request and uses the session information from the cookie to direct traffic to the same real server for subsequent requests.

Servers

Networking

Email

Security

Ecommerce

Load Balancing Service