Load Balancing
DISTRIBUTE TRAFFIC EFFICIENTLY AND INCREASE YOUR UPTIME
WHAT IS LOAD BALANCING?
Load balancing is the process of distributing traffic across multiple servers to make processing tasks more efficient. Load balancers use specialized software to intercept all traffic then redistribute it to a destination server based on a variety of criteria. Criteria could include which server is least utilized, if users are to be sent to a unique landing page, if that user has an active session on a particular server, etc.
WHY USE A LOAD BALANCER?
Load balancers increase uptime by making hardware more efficient.
Choose Your Method
We use round robin by default, but you can choose whichever type of load balancing fits your traffic requirements.
Smart
Load balancing will automatically route traffic to a set of highly available servers. No need to constantly manage traffic distribution.
Secure
All traffic is first processed through our industry leading hardware firewalls then passed to the load balancer which will filter out malicious traffic.
Increase Uptime
Load balancers reduce stress on the individual servers powering your cloud, increasing the likelihood your server will remain online.
Increase Performance
Load balancing can make sure that traffic is distributed to the lowest traffic server making sure your users always experience optimal performance.
Scale Up
As your business grows, so will your traffic. Load balancers will help you manage traffic spikes and provide the infrastructure needed to keep scaling.
LOAD BALANCING SERVICES
2 DIFFERENT PLANS TO MATCH YOUR TRAFFIC NEEDS
CONVENIENT MANAGED LOAD BALANCING
ZebraHost load balancers deploy and scale automatically as needed. Normally, once a load balancer is successfully configured, there is no need to adjust it. But there are times where you need more from your load balancer. Or, you want it configured periodically to optimize performance. The challenge is that you may not understand how to get the best performance out of your load balancer, or have your IT team spend too much time with it.
ZebraHost managed load balancers come with an experienced IT team that will take all the work out of managing your load balancer. Simply let us know what results you need and we will configure your load balancer as required. We will also optimize it for best performance.
WHY SO MANY LOAD BALANCING METHODS?
The goal of load balancing is to speed up service, decrease server load, and stabilize systems by re-routing traffic.
Different website and web apps experience loads under different circumstances. Load balancing methods optimize load based on traffic demands.
ZebraHost Load Balancing solutions enable clients 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.
Load Balancing Methods
Maps client requests to real servers by hashing the source IPs of the request. Client/Server relationships are maintained across ports.
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.
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.
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.
Server with the shortest response time receives the request. As load and response time increases, slower servers begin to field fewer requests.
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.
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.
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.
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.
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.
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.
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.
UNSURE WHICH LOAD BALANCING PLAN IS RIGHT FOR YOU?
Contact our helpful sales team
Sales