5 ms·

In my experience it really comes down to NGINX is trying to position themselves as a replacement for load balancers like F5's BigIPs. So they have functionalit

by breser 9y ago

In my experience it really comes down to NGINX is trying to position themselves as a replacement for load balancers like F5's BigIPs. So they have functionality that goes well beyond what you'd call an HTTP Server. For instance Layer 4 proxying rather than just Layer 7 proxying. But that's just my experience at work. I'm sure there's a ton of other reasons. I can't say that I really agree with your list. I actually find Apache's documentation to be much better, I find myself needing to go read the code to figure out some behaviors with NGINX quite often still. Process isolation with CGI can be equally done with Apache httpd as with NGINX. I can't say I'm familiar with NGINX's caching behavior in detail since we're not using it. Also not sure what you mean by vhosting ecosystem since I see the design as pretty similar, unless you mean the upstream configuration.

tannhaeuser 9y ago
> I actually find Apache's documentation to be much better Err, the points I listed are in favour of Apache httpd (I guess I haven't made myself very clear).
r2dnb 9y ago
Just adding this since nginx proponents seem to be over-represented in threads these days : - I too find that the Apache documentation is much better than the nginx one - I also prefer the Apache License over the open-core, pay-a-license-for-more-feature model of Nginx. - Then the module system of Apache is simply stable, proven, and seamless. I'd go with Apache any time of the day as far as HTTP servers are concerned. I have nothing against Nginx per se, but I think that the Apache is dying / Apache is obsolete rhetoric is so far away from truth and exaggerated that it is almost becoming some sort of propaganda. Apache is doing just fine and is going nowhere anytime soon and its configuration file format is not that complicate. Just try it for yourself and read the (well-written) docs.

by breser 9y ago

tannhaeuser 9y ago

> I actually find Apache's documentation to be much better Err, the points I listed are in favour of Apache httpd (I guess I haven't made myself very clear).

r2dnb 9y ago

Just adding this since nginx proponents seem to be over-represented in threads these days : - I too find that the Apache documentation is much better than the nginx one - I also prefer the Apache License over the open-core, pay-a-license-for-more-feature model of Nginx. - Then the module system of Apache is simply stable, proven, and seamless. I'd go with Apache any time of the day as far as HTTP servers are concerned. I have nothing against Nginx per se, but I think that the Apache is dying / Apache is obsolete rhetoric is so far away from truth and exaggerated that it is almost becoming some sort of propaganda. Apache is doing just fine and is going nowhere anytime soon and its configuration file format is not that complicate. Just try it for yourself and read the (well-written) docs.