Hacker News Reader

I wonder if they had to build the new Gateway Load Balancer in their implementation of this, so they decided to turn it into a product as well.

View on HN

It was a key dependency for this and they also broke it out into a separate product.

This was also something AWS was a couple years behind Azure on.

Azure internal load balancers have some hang ups, but load balancing egress or east-west traffic across security appliances in AWS has always been diabolical in comparison.

I've never used the Geneve protocol, so I can't really tell if this is going to affect which vendors can use the GWLB.

Azure had more specific routing capabilities, yes. But they can't do what this does and maintain the flow stickiness and sessions and scale out.

Makes total sense. I haven't tried it yet but it would have really made life easier for me a couple of years ago. :)

Reply on news.ycombinator.com