11–20 of 33 posts
No surprise, Nginx has much better performance on handling large site and heavy traffic than other web servers. Since it’s required more knowledge and experience to setup and do configurations, that make lots of beginners step away. But time will prove cream always rises to the top.
I'll run Apache till the end.
Considering nginx is really just good at serving static content(maybe CDN uses it a lot) and the rest are all proxying, and Apache can handle static and dynamic contents at the same time, this tells me many web server nowadays are no longer simple http+cgi, but with app servers(e.g. django, rails,etc) running behind a (nginx) proxy so nginx's number takes over apaches.
You can serve dynamic content from nginx too. You don't need Apache in your stack at all.
Whereas with Apache2, PHP/Python/etc. interpreters can run directly in the Apache worker processes. Similarly, you can also run Nodejs/Ruby/Python web application as part of Apache with Passenger module.
Amazing what a more user-friendly interface will do... Looking at you, httpd.conf.
Considering nginx is really just good at serving static content(maybe CDN uses it a lot) and the rest are all proxying, and Apache can handle static and dynamic contents at the same time, this tells me many web server nowadays are no longer simple http+cgi, but with app servers(e.g. django, rails,etc) running behind a (nginx) proxy so nginx's number takes over apaches.
nginx is good at serving dynamic content too. Simple setup with uwsgi for Python and php-fpm for PHP.
Amazing what a more user-friendly interface will do... Looking at you, httpd.conf.
Earlier quoted context omitted.
You can serve dynamic content from nginx too. You don't need Apache in your stack at all.
You can proxy requests from nginx to backend application servers, but you cannot host those applications on the nginx. Whereas with Apache2, PHP/Python/etc. interpreters can run directly in the Apache worker processes. Similarly, you can also run Nodejs/Ruby/Python web application as part of Apache with Passenger module.
Earlier quoted context omitted.
You can proxy requests from nginx to backend application servers, but you cannot host those applications on the nginx. Whereas with Apache2, PHP/Python/etc. interpreters can run directly in the Apache worker processes. Similarly, you can also run Nodejs/Ruby/Python web application as part of Apache with Passenger module.
Is it really an interesting distinction whether PHP is handled via dlopen of mod_php.so or via UNIX sockets to php-fpm?