Paul Graydon <[email protected]> writes: > It seems to me the next most likely solution is to try to combine > either one with dedicated load-balancing software like haproxy or > pound, so that the traffic would go [internet]->[apache/nginx > WAF]->[haproxy/pound]->[web servers]; but part of me really dislikes > the fact that's adding two potentially significant failure points on > each load-balancer instead of one. Maybe I'm worrying too much there > though.
Awhile ago I was running apache+ssl+cache -> haproxy -> appservers. It worked really well. We'd started as just apache and mod-proxy, but there's a queuing problem there, where a slow request would end up blocking the queues. Eventually I wrote off mod-proxy's queuing and just used haproxy. While it is another process to fail, we ran it on the same boxes as apache, and it was all really smooth. seph _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
