---
title: "Comment by Fabio Sarmento on \"A Deep Dive into AWS Load Balancers: CLB, ALB, NLB, and GWLB\" | Hashnode"
description: "While it's true that the Classic Load Balancer (CLB) has significant limitations compared to newer options like the Application Load Balancer (ALB), dismissing"
url: "https://hashnode.com/posts/a-deep-dive-into-aws-load-balancers-clb-alb-nlb-and-gwlb/67e7d695d57bae15082d8ae5/comment/69be8f8baffaa2cb698d9335"
---

[Discussion](https://hashnode.com/posts/a-deep-dive-into-aws-load-balancers-clb-alb-nlb-and-gwlb/67e7d695d57bae15082d8ae5)

Comment [A Deep Dive into AWS Load Balancers: CLB, ALB, NLB, and GWLB](https://hashnode.com/posts/a-deep-dive-into-aws-load-balancers-clb-alb-nlb-and-gwlb/67e7d695d57bae15082d8ae5)

[Fabio Sarmento](https://hashnode.com/@sarmento)

[Mar 21](https://hashnode.com/posts/a-deep-dive-into-aws-load-balancers-clb-alb-nlb-and-gwlb/67e7d695d57bae15082d8ae5/comment/69be8f8baffaa2cb698d9335)

While it's true that the Classic Load Balancer (CLB) has significant limitations compared to newer options like the Application Load Balancer (ALB), dismissing it entirely overlooks scenarios where it might still be useful. For legacy systems that require minimal configuration and basic health checks without the complexities of modern architectures, the CLB can still function adequately, particularly if the application demand is manageable and straightforward.