AWS Network Load Balancer

Re:AWS Network Load Balancer by friendzis on Friday September 08, 2017 @01:04AM (#15197975)

Demo page states "Your browser may keep a connection open for a few seconds and re-use it for a reloaded request. If it does, you'll get the same target", but when I attempted to abuse the power of F5, I was alternated between ice cream and bumblebee.

If you are going to look at it, attempt time - ~04:50 UTC, remote address from 88.119.128.0/20 network

[ Parent | on HN ]

Re:AWS Network Load Balancer by 076ae80a-3c97-4 on Friday September 08, 2017 @06:21AM (#15199134)

Same, got a different one each time.

[ Parent | on HN ]

Re:AWS Network Load Balancer by zob_cloud on Friday September 08, 2017 @03:28PM (#15203264)

Browsers typically use a few connections to load a page so that it can load faster. Each of those threads has a different source port, and thus may route to a different target. In Colm's demo, it depends which thread your browser uses when requesting the part including the CSS which decorates the object. In my Chrome on Mac I see 6 TCP connections to the demo NLB

tcp4 0 0 192.168.100.101.49615 54.69.111.179.80 ESTABLISHED tcp4 0 0 192.168.100.101.49614 54.69.111.179.80 ESTABLISHED tcp4 0 0 192.168.100.101.49613 54.69.111.179.80 ESTABLISHED tcp4 0 0 192.168.100.101.49612 54.69.111.179.80 ESTABLISHED tcp4 0 0 192.168.100.101.49611 54.69.111.179.80 ESTABLISHED tcp4 0 0 192.168.100.101.49610 54.69.111.179.80 ESTABLISHED

Each of those will be routed to the same target, so it's up to your browser to decide which to use for what.

[ Parent | on HN ]