---
title: "Comment by Wily Ktpm 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 NLB to handle a spike in TCP traffic, and the performance difference in latency was immediate"
url: "https://hashnode.com/posts/a-deep-dive-into-aws-load-balancers-clb-alb-nlb-and-gwlb/67e7d695d57bae15082d8ae5/comment/69d700a26be3bf763e57f809"
---

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

[Wily Ktpm](https://hashnode.com/@wilyktpm)

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

Great deep dive. I recently migrated a legacy app from a CLB to an NLB to handle a spike in TCP traffic, and the performance difference in latency was immediately noticeable, just as you outlined. Your explanation of the NLB's flow hash routing versus the ALB's content-based routing perfectly captures that key architectural decision point.