---
title: "Comment by For sell Mx on \"A Deep Dive into AWS Load Balancers: CLB, ALB, NLB, and GWLB\" | Hashnode"
description: "Great deep dive! I recently migrated a legacy app from a CLB to an ALB specifically for the path-based routing, and the difference in managing our microservices"
url: "https://hashnode.com/posts/a-deep-dive-into-aws-load-balancers-clb-alb-nlb-and-gwlb/67e7d695d57bae15082d8ae5/comment/69d795096d881276c5bec60a"
---

[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)

[For sell Mx](https://hashnode.com/@mxsell)

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

Great deep dive! I recently migrated a legacy app from a CLB to an ALB specifically for the path-based routing, and the difference in managing our microservices was night and day. Your explanation of the NLB's static IPs also solved a puzzle we had with a third-party firewall whitelist.