||Each request is sent to the next available server sequentially.
||The most basic form of load balancing, this can be used when your servers have the exact same hardware configuration and your user sessions are based on session cookies. This is the default load balancing option; an alternative which is highly recommended is Least Connections.
||Requests are distributed to servers based on a hash of the End-User Visitor's first three segments of their IP Address (Class C Network).
||This method is recommended if you do not utilize session cookies, and instead base the session off of the incoming source IP. The DOSarrest Proxy incoming IP address may be different for each user, but each user will arrive at the same server on your side regardless of which DOSarrest proxy they are filtered through. We do not recommend this method if you use session cookies, as there will be more of uneven load.
||Each request is sent to the server that is currently utilizing the least amount of connections.
||This method will produce the most even amounts of load, as we will literally be sending the next request to the server which has the most available resources.
||Requests are distributed to servers based on a weight configured individually for each server.
||This method is recommended if your servers do not have similar hardware configurations, and you wish to send 20% to one server, and 80% to another. This is useful if you are utilizing servers from different providers, such as two VPS hosting environments, one in Europe, and another in North America. If each of your servers are identical, use Least Connections or Round Robin. If each of your servers are similar but not identical, use Least Connections.
|By Domain (route requests to different servers based on domain)
||Requests are distributed to Load balanced Groups or single servers, based on the Domain (Host Header) the End User Visitor is requesting.
||You can use this method if you have more than one domain that are running on different servers or different IP addresses. As long as the domains not require an SSL certificate, or they share the same SSL certificate (SAN, Wildcard) you can utilize a single VIP Address. This will save money overall without needing to purchase an additional VIP Address for additional domains/server combinations. You can also use this feature to enable different settings for different domains, while maintaining the same Load Balanced Group or server IP.
|By Resource(www.mydomain.com/images/ goes to 1 IP, www.mydomain.com/ goes to a different server/IP)
||Requests are distributed to load balanced groups or single servers, based on the URI or Path the End User Visitor is requesting.
||You can use this method if you have, or would like, separate servers for different kinds of content, or different URI Paths. This affects all domains unless configured in combination with the above "By Domain" feature to establish different settings for different domains.