News for hackers. Stuff that matters.

A comment on AWS Network Load Balancer. Parent comment

Re:AWS Network Load Balancer by takeda on Thursday September 07, 2017 @08:31PM (#15197034)
Chances are it's IPVS[1], maybe with some patching.

Why would one reinvent the wheel when Linux already lets you do that.

In that case it would be C since it's implemented in the Linux kernel.

[1] https://en.wikipedia.org/wiki/IP_Virtual_Server

[ Parent | on HN ]
Re:AWS Network Load Balancer by takeda on Friday September 08, 2017 @12:36AM (#15197874)
I should have read the blog instead of skimming before responding.

This appears as Layer 4 load balancing, IPVS is more of Layer 3.

So the person who was voted down by mentioning HAProxy might not be too far off. It could be implemented through HAProxy + TPROXY enabled in the kernel[1]. Then just make sure that default gateway configured on targets routes back to the load balancer or it is the load balancer.

[1] https://www.loadbalancer.org/blog/configure-haproxy-with-tpr...

[ Parent | on HN ]
Re:AWS Network Load Balancer by bogomipz on Friday September 08, 2017 @03:33AM (#15198492)
>"This appears as Layer 4 load balancing, IPVS is more of Layer 3."

No, IPVS is L4 load balancing. L3 load balancing would be a routing protocol plus ECMP.

[ Parent | on HN ]
Re:AWS Network Load Balancer by takeda on Sunday September 10, 2017 @04:24AM (#15211327)
Ah my bad, even the wiki link I posted said it is layer 4. I guess both solutions could be utilized then, perhaps it was IPVS then since it would be more performant than HAProxy.
[ Parent | on HN ]