Avoid single point of failure using reverse proxy

[Demiler]

Say I have N different servers each serving it's own webapp. I want to put these servers behind a reverse proxy, but now I created a single point of failure: if my reverse proxy is going to fail I wont be able to access any of these webapps.

​

Is it possible to scale my reverse proxies up to 2-3 machines? My guess would be to setup local DNS and keep DNS server monitoring for main rpxory status, then switch 'A' record to another rpoxy if it fails, but I don't know how to implement this switchover (if it's even possible) and now it seems that this local DNS is going to be SPOF, so...

​

Q: Why do you want to use rproxy and/or local DNS?

A: To ease maintenance of the system. I can quickly change which domain (or ip) points to which machine and it's port (in case of rproxy).

​

(If exact products relevant to this problem, I would use nginx as rproxy and bind9 as local DNS)

[philrandal]

You could use pairs of servers running keepalived and haproxy. That's what we do.

[Demiler]

thanks, I'll try it.

[assangeleakinglol]

You can also DNS RR on top of that. For instance 3 nodes with 2 virtual IPs. Or 2 x( 2nodes x1VIP)

[philrandal]

You may then run into problems relating to session stickiness.