Hi all, We use a pair of servers as load balancers, using Apache HTTPD & mod_proxy. Ideally I'm looking to transition away from Apache HTTPD if possible and on to something a little less resource hungry and specifically designed for the role. It's going to have to be a slow transition because we're combining multiple aspects in httpd, such as LDAP auth, rewrites, some direct PHP hosting and captcha bits, for just over 60 vhosts.
What I'm looking at at the moment is to stick something flexible, caching (to reduce back end traffic) and capable of reverse proxying in front of httpd. The idea being to initially proxy through to httpd on the same box and then over a period of time have vhosts migrated over to it much as possible. It does also need to produce NCSA or Apache httpd compatible logs for urchin processing. I've been experimenting with Varnish to varying levels of success, combined with Pound acting as an SSL intermediary, but some former colleagues from a previous role suggest I consider Apache Traffic Server. The blurb on the website looks very interesting, but unlike Varnish I've not heard much from sysadmins about having actually used it. Does anyone have any recommendations or thoughts about ATS vs Varnish, or thoughts about other products that may be more suited? Am I about to unleash a whole world of hurt on myself? Paul _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
