News for hackers. Stuff that matters.
Re:Setting Up HTTP(S) Load Balancing – WebSocket proxy support by toast0 on Tuesday April 25, 2017 @09:13AM (#14193143)
> This is not basic - load balancing needs to be more reliable than the service behind it, which is hard to do. You can run your own instances with nginx or haproxy but you'll never get to the same reliability, scale and performance without a significant amount of work.

It really depends on the reliability of your underlying servers; it's pretty easy to get nginx or haproxy to be reliable: get your config set and don't touch it. Then you're just down to hardware issues, which are generally fairly rare. If you need to mitigate hardware issues, you'll need to do something fancy with IP takeover/ECMP etc, which I agree is a significant amount of work.

The one thing that people really need to think about though is when you let other people do TLS termination on your behalf, you're putting the private information of your customers into the hands of someone else -- they could disclose it due to bugs in their system, rogue employees, system intruders, etc. Layer 7 load balancing features can be nice, but they come at a price. This is something to consider even if your load balancer is provided by the same people providing your servers.

Re:Setting Up HTTP(S) Load Balancing – WebSocket proxy support by user5994461 on Tuesday April 25, 2017 @09:49AM (#14193462)
Then haproxy/nginx is your single point of failure and you need to put a load balancer in front. Back to square one.

The usual way to have failover on load balancers is VRRP [1] and that doesn't work well in the cloud.

[1] Also known as HSRP, VRRP, keepalived, CARP

Re:Setting Up HTTP(S) Load Balancing – WebSocket proxy support by stephenr on Tuesday April 25, 2017 @10:51AM (#14194020)
Decent VPS/Rented Dedi providers, and surely all Colo providers can provide IP failover.

Edit: my point is, if a "cloud" load balancer can't provide the features you want (e.g. TLS SNI) and the "cloud" VM's can't provide the features you need to run your own LB (e.g. IP failover) maybe this is an opportunity to learn that the "cloud" isn't some golden goose shitting out golden eggs.