Hi Angelo.
------ Originalnachricht ------
Von: "Angelo Hongens" <ang...@hongens.nl>
An: haproxy@formilux.org
Gesendet: 05.01.2018 11:49:55
Betreff: Re: haproxy without balancing
On 05-01-2018 11:28, Johan Hendriks wrote:
Secondly we could use a single ip and use ACL to route the traffic to
the right backend server.
The problem with the second option is that we have around 2000
different
subdomains and this number is still growing. So my haproxy config will
then consists over 4000 lines of acl rules.
and I do not know if haproxy can deal with that or if it will slowdown
request to much.
Maybe there are other options I did not think about?
For me the second config is the best option because of the single IP,
but i do not know if haproxy can handle 2000 acl rules.
I would choose the second option. I don't think the 2000 acls is a
problem. I've been running with more than that without any problems.
A single point of entry is easiest.
We run a lot of balancers with varnish+hitch+haproxy+corosync for
high-available loadbalancing. Perhaps high-availability is not a
requirement, but it's also nice to be able to do maintenance during the
day and have your standby node take over..
Just for my curiosity why hitch and not only haproxy for ssl
termination?
--
met vriendelijke groet,
Angelo Höngens
Regards
Aleks
