Comment

Comment on What load balancers can do HA (preferably open source, web gui)

just_another_person@lemmy.world ⁨9⁩ ⁨months⁩ ago

If your requirement is a GUI, you’re not going to find anything. HA Proxy is also the most performance out of anything out there last I looked, and it’s got one of the simplest configuration setups.

Traefik: kinda slow, mostly meant for large numbers of microservices, pretty verbose configuration
Envoy: middle of the road, also most meant for cloud services, but should work with anything
nginx: does have a popular 3rd party GUI, seems to be confusing for most that don’t work with it a lot
caddy: fewer LB specific options if you’re just talking about service routing and response time, pretty easy to confirm for most, and some sort of decent 3rd party UIs, but they won’t have all the options available.

source

Sort:hotnew top

irotsoma@lemmy.blahaj.zone ⁨9⁩ ⁨months⁩ ago
Personally, I find Traefik much simpler than Nginx, especially with Kubernetes, but even with pure docker, but it’s definitely not as performant. That’s balanced by the fact that it does a lot of automatic detection and has dynamic config loading so I don’t have to break other services when changing configurations.

source
sugar_in_your_tea@sh.itjust.works ⁨9⁩ ⁨months⁩ ago
I use HAProxy and Caddy, and for different reasons:

HAProxy - sni-based proxying to devices on my VPN; lives on my VPS

Caddy - TLS-trunking (and cert renewal) per device and reverse proxy in front of containers

It works really well. My router is configured as a DNS server to route my domains to my local network, so I get to use TLS even on my LAN, which is neat.
source
magikmw@lemm.ee ⁨9⁩ ⁨months⁩ ago
I can confirm caddy is more of a high availability proxy than a proper load balancer, but it does it’s job and has an api you can hook up to a gui if you want. Or like I do - to a config repo with ci/cd deployment.

source
vegetaaaaaaa@lemmy.world ⁨9⁩ ⁨months⁩ ago
apache can do load balancing as well httpd.apache.org/docs/…/mod_proxy_balancer.html

I’d pick something that you already use across your stack, to minimize the number of different integration/config styles/bugs…

source