How about
h2o
cherokee.org
and nginx and lighttpd are fast
apache with event mpm
any recent benchmarks by anyone on 14?
does varnish cache make this all moot?
Why not both? Front end HAProxy splits traffic up to different sets of front end webservers, a set for dynamic content and a set for static content. The dynamic set has servers for PHP, Rails, Java, whatever you need. The static content is directed to a pair of heavy duty varnish servers that cache the content coming from a large, but relatively slow, fileserver. Database access can also be load-balanced through HAProxy over a couple of read-only slaves, with writes going to a single read/write master.I like haproxy for that..... I wonder would varnish cache do that for me or is it better to use haproxy as well?
I was wondering if varnish does load balancing as well as haproxy to 2 bird one stoneWhy not both? Front end HAProxy splits traffic up to different sets of front end webservers, a set for dynamic content and a set for static content. The dynamic set has servers for PHP, Rails, Java, whatever you need. The static content is directed to a pair of heavy duty varnish servers that cache the content coming from a large, but relatively slow, fileserver. Database access can also be load-balanced through HAProxy over a couple of read-only slaves, with writes going to a single read/write master.
Sure, it can. You can also configure nginx as a load-balancing reverse proxy. And use nginx for frontends and backends alike. But I also like using the best tool for each job. Also homogeneity is a bad idea from a security perspective. That's why Netflix uses a whole bunch of different operating systems for a whole bunch of different jobs.I was wondering if varnish does load balancing as well as haproxy to 2 bird one stone
It depends on the situation. Scalability comes to mind. It's always good to keep any future growth into account when designing the infrastructure for a particular purpose. But sure, don't add any unnecessary complexity.simplification fewer moving parts
You are confirming kinda what I though insincively from experence!Sure, it can. You can also configure nginx as a load-balancing reverse proxy. And use nginx for frontends and backends alike. But I also like using the best tool for each job. Also homogeneity is a bad idea from a security perspective. That's why Netflix uses a whole bunch of different operating systems for a whole bunch of different jobs.
It depends on the situation. Scalability comes to mind. It's always good to keep any future growth into account when designing the infrastructure for a particular purpose. But sure, don't add any unnecessary complexity.