[auxbuss]

I'm not biased one way or the other, although I find nginx far easier to work with than apache. And like many here, I've been working with apache forever.

1. I have no problem consolidating logs. I don't know your particular use case, though, so maybe you have an edge case that is tricky with nginx.

2. I tried using native wsgi on nginx and didn't enjoy it. So, I switched to gunicorn. Problem solved. I run graphite and its clan via gunicorn as a key process in many places; it's rock solid.

3. php fpm as a proxy behind nginx performs just as well as mod-php on apache, if not better. It's a damn sight easier to scale.

So, I don't share your concerns about nginx. So far, I have found no reason to reason to continue with apache.

The biggest win has been serving a huge throughput of static images for a particular client's web-site. We sized a new machine under apache, but when we deployed with nginx, it used a tiny percentage of apache's resources.

It's hard not to like nginx.