3 ms·
> HAProxy 2.2 for terminating TLS connections, and load balancing between app servers. Enables easy rolling updates of application servers. Wonder why he is no
by fasteo 4y ago
> HAProxy 2.2 for terminating TLS connections, and load balancing between app servers. Enables easy rolling updates of application servers.
Wonder why he is not using hetzner's load balancer [1]. At least cost-wise, the savings are huge (4xAX41-NVME are around 160€; LB31 - the most expensive one - is 36€)
[1] https://www.hetzner.com/cloud/load-balancer https://www.hetzner.com/cloud/load-balancer
- baobob 4y agoThat product has a serious lack of docs, and I know from experience some off-cloud vendor balancers have crappy architectures with low overall throughput limits. Their product could be a shared CPU VPS under the hood or something deeply baked into their network architecture, guilty until proven innocent
- withinboredom 4y agoI believe the load balancer is pretty new and it is probably the only service that allows connecting to dedicated servers -- which is separate from their cloud offering.
- fnomnom 4y agoi tried to use it out of curiosity but the documentation was really lacking and the workflow of creating the networks is bad
- tyingq 4y agoIt's kind of interesting that there's more horsepower/cores in the load balancers than in the downstream web/app servers...4xAX41 vs 3xAX41. So I imagine something is different about the workload there versus a typical load balancer.
- dolmen 4y agoThe load balancer is at the core of the product reliability. That seems a good reason to completely control it instead of relying on a black box.
- matteocontrini 4y agoHetzner's LB doesn't really scale. LB31 should be based on CX31 which is just 2 vCPU compared to the 12 threads of a single AX41 dedicated server.