4

I am trying to understand what are the key differences are between ALB (Application Load Balancer) and NLB (Network Load Balancer). I understand that ALB is at layer 7 on the OSI model -- this means it exists at the application level -- and the NLB is at layer 4 which means it works at the transport level.

That being said, this means that the ALB can only handle HTTP/HTTPS requests, unlike the NLB that can handle any type of TCP requests.

So my question is... is that all? Or are there any other differences?

10

Network load balancing is the distribution of traffic based on network variables, such as IP address and destination ports. It is layer 4 (TCP) and below and is not designed to take into consideration anything at the application layer such as content type, cookie data, custom headers, user location, or the application behavior. It is context-less, caring only about the network-layer information contained within the packets it is directing this way and that.

Application load balancing is the distribution of requests based on multiple variables, from the network layer to the application layer. It is context-aware and can direct requests based on any single variable as easily as it can a combination of variables. Applications are load balanced based on their peculiar behavior and not solely on server (operating system or virtualization layer) information.

The difference between the two is important because network load balancing cannot assure availability of the application. This is because it bases its decisions solely on network and TCP-layer variables and has no awareness of the application at all. Generally a network load balancer will determine “availability” based on the ability of a server to respond to ICMP ping, or to correctly complete the three-way TCP handshake. An application load balancer goes much deeper, and is capable of determining availability based on not only a successful HTTP GET of a particular page but also the verification that the content is as was expected based on the input parameters.

This is also important to note when considering the deployment of multiple applications on the same host sharing IP addresses (virtual hosts in old skool speak). A network load balancer will not differentiate between Application A and Application B when checking availability (indeed it cannot unless ports are different) but an application load balancer will differentiate between the two applications by examining the application layer data available to it. This difference means that a network load balancer may end up sending requests to an application that has crashed or is offline, but an application load balancer will never make that same mistake.

Reference:

Network Load Balancing versus Application Load Balancing

  • 2
    i will only correct this by saying that based on AWS documentation, the ALB has healthchecks, so it can check avilability of the application, also found this table that gives a good explanation of the benefits of each LB aws.amazon.com/elasticloadbalancing/details/?nc1=h_ls – Diego Velez Nov 6 '17 at 17:46
  • 1
    Agree... this misses some of the nuances specific to the AWS NLB implementation and points out some capabilities of application load balancers in general that are not part of AWS ALB. – Michael - sqlbot Nov 6 '17 at 22:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.