Load Balancer vs ADC: What Is the Difference?

What a load balancer does, what an application delivery controller adds, and how to choose for your applications.

Technician sliding a network module into an equipment chassis

When one server can no longer carry an application, or the application is too important to depend on one server, you add a second. Now something has to sit in front and decide which server answers each user. That device is a load balancer. Its more capable relative is the application delivery controller, or ADC.

The two terms are often used as if they meant the same thing. They do not, and the difference affects what you should buy.

What a load balancer does

A load balancer presents one address to users and shares their connections among several servers behind it. It has three core functions.

Distribution. Common methods are:

  • Round robin: each new connection goes to the next server in turn
  • Least connections: each new connection goes to the server with the fewest active ones
  • Source address: the same user always reaches the same server
  • Weighted: stronger servers receive a larger share

Health checks. The load balancer tests each server every few seconds and stops sending traffic to one that does not answer.

Persistence. Some applications need a user to stay on the same server for the whole session. The load balancer remembers which server each user was given.

A basic load balancer works at layer 4 of the network model. It sees IP addresses and port numbers, not the content of the request. That makes it fast and simple.

What an ADC adds

An application delivery controller is a load balancer that understands the application itself, at layer 7, and adds services around it.

  • SSL/TLS offloading. The ADC handles the encryption, so certificates are managed in one place and the servers are relieved of that work.
  • Content-based routing. Requests are sent to different groups of servers according to the web address, host name or cookie.
  • Compression and caching. Pages load faster and the servers do less.
  • Web application firewall (WAF). Attacks such as SQL injection and cross-site scripting are blocked before they reach the application.
  • Global server load balancing (GSLB). Users are directed to the right data center, or to the disaster recovery site when the main one is down.
  • Application-aware health checks. The ADC requests a real page and checks the answer, not only whether the port is open.

Side by side

Basic load balancer ADC
Works at Layer 4 (TCP and UDP) Layers 4 to 7
Decides by IP address and port Web address, host name, cookies and headers
Health check Is the port open? Does the application answer correctly?
Encryption Passed through to the servers Offloaded and inspected
Security Minimal WAF and rate limiting
Multiple sites No GSLB

Which one do you need?

A basic load balancer is enough for simple services: DNS, RADIUS or LDAP servers, or a pair of internal servers with no special requirements.

An ADC is the better choice when:

  • The application faces the internet, such as a customer portal or an online service
  • Many users depend on a web-based ERP, HR or banking application
  • You want certificates managed in one place
  • You need a web application firewall in front of the application
  • You run a second data center or a disaster recovery site

Hardware, virtual or cloud

  • Hardware appliances give dedicated performance and hardware acceleration for encryption. They suit heavy traffic.
  • Virtual appliances run on your existing virtualization platform. They suit most mid-sized deployments and are easy to scale.
  • Cloud load balancers are the natural choice for applications hosted in a public cloud.

Products on the market

Commercial ADCs include Fortinet FortiADC, F5 BIG-IP, NetScaler, A10 Thunder and Kemp LoadMaster. Open-source software such as HAProxy and NGINX handles load balancing and reverse proxying well when you have the skills in-house to run it.

Features overlap heavily at this level. Local support, licensing terms and how well the product fits your existing network usually decide the choice.

Sizing an ADC

Collect these numbers before comparing models:

  • Concurrent connections and new connections per second
  • Throughput in megabits or gigabits per second
  • SSL/TLS transactions per second, which is often the first limit reached
  • Throughput with the web application firewall switched on
  • Expected growth over the next three years

Common mistakes

  • One ADC on its own. A single load balancer becomes the new single point of failure. Deploy a pair in high availability.
  • Ping-only health checks. A server can answer a ping while the application on it has stopped.
  • Forgetting the database. Balancing three web servers does not help if they all depend on one database server.
  • Losing the client address. Behind an ADC, the servers may see only the ADC's address. Pass the real one in the X-Forwarded-For header so that the logs stay useful.
  • Expired certificates. Offloading puts every certificate in one place. Monitor the expiry dates.

How Arqi Networks can help

Arqi Networks designs and deploys load balancing and ADC solutions for businesses across Pakistan. As an official Fortinet partner we supply and support FortiADC, and we also work with the other ADC brands used in the market.

The same team handles servers and storage and network security, so the design covers the whole path from the firewall to the servers.

Back to all articles
Keep Reading

More Articles

Need your application to stay online?

Tell us about the application, its users and its servers, and we will recommend the right load balancing design.

Need Help? Chat with us