UPDATES

Wizertech Informatics Pvt Ltd is An ISO 9001:2008 and ISO 14001:2004 certified IT Infrastructure Consultancy & System Integration company having presence all across India.

Home » SOLUTION » IP Infrastructure Solutions » Load Balancing

Load Balancing

Technology Overview

Hardware and software load balancers can come with a variety of special features.

  1. Asymmetric load: A ratio can be manually assigned to cause some backend servers to get a greater share of the workload than others. This is sometimes used as a crude way to account for some servers being faster than others.
  2. Priority activation: When the number of available servers drops below a certain number, or load gets too high, standby servers can be brought online
  3. SSL Offload and Acceleration: SSL applications can be a heavy burden on the resources of a Web Server, especially on the CPU and the end users may see a slow response (or at the very least the servers are spending a lot of cycles doing things they weren’t designed to do). To resolve these kinds of issues, a Load Balancer capable of handling SSL Offloading in specialized hardware may be used. When Load Balancers are taking the SSL connections, the burden on the Web Servers is reduced and performance will not degrade for the end users.
  4. Distributed Denial of Service (DDoS) attack protection: load balancers can provide features such as SYN cookies and delayed-binding (the back-end servers don’t see the client until it finishes its TCP handshake) to mitigate SYN flood attacks and generally offload work from the servers to a more efficient platform.
  5. HTTP compression: reduces amount of data to be transferred for HTTP objects by utilizing grip compression available in all modern web browsers
  6. TCP offload: different vendors use different terms for this, but the idea is that normally each HTTP request from each client is a different TCP connection. This feature utilizes HTTP/1.1 to consolidate multiple HTTP requests from multiple clients into a single TCP socket to the back-end servers.
  7. TCP buffering: the load balancer can buffer responses from the server and spoon-feed the data out to slow clients, allowing the server to move on to other tasks.
  8. Direct Server Return: S an option for asymmetrical load distribution, where request and reply have different network paths
  9. Health checking: S the balancer will poll servers for application layer health and remove failed servers from the pool.
  10. HTTP caching: the load balancer can store static content so that some requests can be handled without contacting the web servers.
  11. Content Filtering: some load balancers can arbitrarily modify traffic on the way through.
  12. HTTP security: some load balancers can hide HTTP error pages, remove server identification headers from HTTP responses, and encrypt cookies so end users can’t manipulate them.
  13. Priority queuing: also known as rate shaping, the ability to give different priority to different traffic.
  14. Content aware switching: most load balancers can send requests to different servers based on the URL being requested.
  15. Client authentication: authenticate users against a variety of authentication sources before allowing them access to a website.
  16. Programmatic traffic manipulation: at least one load balancer allows the use of a scripting language to allow custom load balancing methods, arbitrary traffic manipulations, and more.
  17. Firewall: direct connections to backend servers are prevented, for network security reasons
  18. Intrusion Prevention System: offer application layer security in addition to network/transport layer offered by firewall security.