Hello.
First off all I wish everyone a really good 2018. And hopefully 2018
will serve a lot of good memory's.

BTW if this is the wrong list please excuse me.

We have an application running over multiple servers which all have
there own subdomain, there are about 12 of them.
We can live without loadbalancing, so there is no failover, each server
serves a couple of subdomains.
At this moment every server has its own ip, and so every subdomain has a
different DNS entry. What we want is a single point of entry and use
haproxy to route traffic to the right backend server.
Replacing an server is not easy at the moment. We have a lot of history
to deal with. We are working on it to leave that behind but till then we
need an solution.


I looked at this and i think i have two options.
Create for each server in the backend an ip on the haproxy machine and
connect a frontend for that IP to the desired backend server.
This way we still have multiple ipadresses, but they can stay the same
if servers come and go.

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.

Thank you for your time.

Regards
Johan


Reply via email to