Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Network Load Balancer

aws.amazon.com

Post reply on HN
Print view View original

11–20 of 122 posts

Re: AWS Network Load Balancer

#14

Post by tyingq »

Cieplak wrote: post #9

I wonder what they wrote it in. I'd guess C++, Java or Erlang, or a combination of those.

It preserves source ip, so that suggests something like a kernel module, or like Intel's DPDK. Either (practically) rules out anything but C, doesn't it?

Re: AWS Network Load Balancer

#15

Post by irl_zebra »

colmmacc wrote: post #2

If you're curious to see NLB in action, here's a live demo: http://nlb-34dc3b430638dc3e.elb.us-west-2.amazonaws.com/ , it took about 5 minutes in the console to set it up and no changes on the targets/backends. Massive disclaimer: I work on NLB.

Any idea how long for GovCloud?

Re: AWS Network Load Balancer

#16

Post by Thaxll »

tyingq wrote: post #14
Cieplak wrote: post #9

I wonder what they wrote it in. I'd guess C++, Java or Erlang, or a combination of those.

It preserves source ip, so that suggests something like a kernel module, or like Intel's DPDK. Either (practically) rules out anything but C, doesn't it?

Or they could just encapsulate the packet to preserve the IP...

Re: AWS Network Load Balancer

#17

Post by colmmacc »

Thaxll wrote: post #13

When is http2 coming to ELB ... :/ It should be their #1 priority.

ELB's Application Load Balancer (ALB) supports HTTP/2 termination. More in the original launch announcement: https://aws.amazon.com/blogs/aws/new-aws-application-load-ba... and https://aws.amazon.com/elasticloadbalancing/details/#details

Re: AWS Network Load Balancer

#19

Post by discodave »

uji wrote: post #7
g09980 wrote: post #3

This was discussed a couple of times recently, but answers seemed contradictory. ELB requires pre-warming if you expect sudden high load. But do ALB and NLB? [1] https://news.ycombinator.com/item?id=15085863 [2] https://news.ycombinator.com/item?id=14052079

Seems like this limitation has been for long time (since 2009). Curious to know how everyone has been using ELB. To me, ELB seems to be an unfinished product. It must be painful to first predict heavy load on your application and then notify AWS well in advance.

It's almost like AWS released what they thought was the best product at the time, regretted some of their decisions and then launched other product(s) to replace it....

In this case, it seems like the one-size-fits-all ELB has been replaced by ALB for those using containers, who want L7 LB, and don't need insanity-scale. NLB for those who want massive scale, a dumb pipe and/or need consistent IPs. They could have tried to build these features into ELB but they didn't, they deliberately created new nomenclature to get rid of baggage.

Also see: SimpleDB -> DynamoDB. EC2 Classic -> VPCs.

Post reply on HN