22
I see a lot of people recommending Nginx on Apache [HTTP Server], and I can well understand why the first is Event-driven it brings advantages as to scalability (i.e. low memory consumption under heavy load) compared to the approach process-based of the second. But I’m not sure about its disadvantages, or cases where Apache would be a better solution. Citing for example this site (that talks a lot about Nginx but almost nothing about Apache):
Apache is like Microsoft Word, it has a million options but you only need six. Nginx does these six things, and five of them 50 times faster than Apache.
What situations then would Apache be the best solution? Or: what are the main points of difference between them, which can be key to the choice between one and the other in a given situation?
I miss an explanation about "what are the main points of difference between them [...]", as requested in the question...
– brasofilo
If you evaluate Views you will always find the items "Performance", "Security" and "Scale" as differential. Take an example: http://blog.corujadeti.com.br/nova-versao-do-apache-2-4-versus-nginx-fight/
– gpupo
I wanted to say that I miss in the context of this site, without having to go to another site to learn something new, but thanks for the reference ;)
– brasofilo
See the issue with the inclusion of numbers
– gpupo
This graph with the/second requests with PHP does not say whether mod_php or Fastcgi was used. Should this not be taken into consideration? If not, why?
– Gustavo Piucco
Yes, it should be taken into consideration if you choose to use PHP after this performance study. But these details you can question in the IT Owl blog that ran the tests, okay? A hug!
– gpupo