NGINX scores $20 MEELLLION to remind people it sells stuff Web-server-maker NGINX has a tricky problem: its software is used by the likes of Netflix and Dropbox, it can claim 40 per cent of the world's top 1,000 web as users, but that ability to operate at extraordinary scale isn't translating into the hoped-for level of sales of its commercial products and services. The for-cash …
having looked at that page, and also based on experience, you're right with respect to PHP but "generic" serving is typically faster with Nginx. Not always, of course. The best results I usually get are Nginx and Apache working together .... surprise surprise, horses for courses and all that ...
but "generic" serving is typically faster with Nginx
Versus which Apache MPM?
More generally, Apache is so configurable that "Apache versus Nginx" is pretty much meaningless, even for a given workload.
I have nothing against Nginx, mind you; but some people seem to regard it as some magical innovation, as if there were no other event-driven servers out there. It's a well-understood architecture that's been around for at least a couple of decades. I've written a commercial event-driven multiprotocol server myself. Nothing terribly remarkable.
Just because Redhat can make a successful business of commercial Linux doesn't make it a business model that works for all.
In the webserver space, Covalent used to offer Apache with a similar business model. It works better as a small component of a wider portfolio (which is really what Redhat offers). It may be that nginx.com will go the way of Covalent and get bought by someone bigger.
nginx is a good product (and tengine - the chinese version - improves it). But some of the evangelism that compares it extremely favourably to apache (generally in configurations no apache person would recommend, such as mod_php) won't stand up to the scrutiny of going mainstream.
Apache is pretty much outdated. The conf settings are bizarre, the multi-process model might have been relevent in 1995 and you end up having to faff with shared memory. One thread per request... please.
Try find sample code that reads a request body... WTF is a brigade...
The documentation is woeful
I say there biggest problem is that Apache is understood and works fine, plus it tends to be a defacto standard in many distros. I've played NGINX and in general the way I see it, it's not spectacular enough for me to uninstall Apache and replace it withe NGINX, The "Speed" things is rarely a pain point for most of our applications.
Granted if RHEL or what not, had NGINX installed by default I'd probably say the same thing about Apache.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
