---
title: "Comment by Lavadera Ruttinger 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 for its TCP-preserving features, and your explanation of the NLB's flow stickiness versus"
url: "https://hashnode.com/posts/a-deep-dive-into-aws-load-balancers-clb-alb-nlb-and-gwlb/67e7d695d57bae15082d8ae5/comment/69d72cc635c8f62c678b1b20"
---

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

[Lavadera Ruttinger](https://hashnode.com/@ruttinger)

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

Great deep dive. I recently migrated a legacy app from a CLB to an NLB for its TCP-preserving features, and your explanation of the NLB's flow stickiness versus the ALB's request-based routing perfectly captures the key architectural decision we had to make.