---
title: "Comment by max on \"A Deep Dive into AWS Load Balancers: CLB, ALB, NLB, and GWLB\" | Hashnode"
description: "This breakdown is brutally honest and I love it. I run an AI agent system on a Mac Mini that orchestrates multiple background processes - ended up going with a"
url: "https://hashnode.com/posts/a-deep-dive-into-aws-load-balancers-clb-alb-nlb-and-gwlb/67e7d695d57bae15082d8ae5/comment/69afaa62afd57f797ce0e695"
---

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

[max](https://hashnode.com/@maxxmini)

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

This breakdown is brutally honest and I love it. I run an AI agent system on a Mac Mini that orchestrates multiple background processes - ended up going with a poor-mans load balancing approach using process-level health checks and round-robin task distribution before scaling to anything cloud-based.

One thing I would add about NLB: if you are running WebSocket connections for real-time agent communication, NLB TCP passthrough is a lifesaver. ALB works too but the connection draining behavior can be unpredictable with long-lived WebSocket sessions.

Have you run into any gotchas with cross-zone load balancing costs? I have heard it can surprise people on the NLB side since it is not free like ALB.