21–30 of 122 posts
I wonder what they wrote it in. I'd guess C++, Java or Erlang, or a combination of those.
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.
Earlier quoted context omitted.
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...
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?
Also did I read it wrong or this is actually cheaper than ALB?
Awesome! Can't wait to dig in more!
I love the concept, because not being able to handle TCP traffic was one shortcoming of the new ALB. But that pricing model: Bandwidth – 1 GB per LCU. New Connections – 800 per LCU. Active Connections – 100,000 per LCU. Would be nice to have it added to the simple monthly calculator: https://calculator.s3.amazonaws.com/index.html but I had to read the FAQ to find out what those were: https://aws.amazon.com/elasticloa…
---
An LCU is a new metric for determining how you pay for a Network Load Balancer. An LCU defines the maximum resource consumed in any one of the dimensions (new connections/flows, active connections/flows, and bandwidth) the Network Load Balancer processes your traffic.
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.
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
Earlier quoted context omitted.
Or they could just encapsulate the packet to preserve the IP...
Happy to be educated. There's some easy way to alter the destination IP that way?
This is heavily used by Facebook for their loadblancer on their racks.
I love the concept, because not being able to handle TCP traffic was one shortcoming of the new ALB. But that pricing model: Bandwidth – 1 GB per LCU. New Connections – 800 per LCU. Active Connections – 100,000 per LCU. Would be nice to have it added to the simple monthly calculator: https://calculator.s3.amazonaws.com/index.html but I had to read the FAQ to find out what those were: https://aws.amazon.com/elasticloa…