i note postfix usurped sendmail much faster.
funnily enough nginx also is a IMAP/POP3 proxy server
Nginx has replaced Apache as the most used web server among the top 10,000 sites
31–40 of 76 posts
Re: Nginx has replaced Apache as the most used web server among the top 10,000 sites
#32can someone link up a good "nginx for newbies" type resource for someone who is familiar with programming?
I hope it's kosher that I link my own blog since it deals specifically with nginx: http://blog.martinfjordvald.com/2010/07/nginx-primer/
This is one of the best primers you get for getting started with Nginx, and mfjordvald is a genuinely nice and helpful guy!
Re: Nginx has replaced Apache as the most used web server among the top 10,000 sites
#33Earlier quoted context omitted.
Nginx is used as a reverse proxy for less strong application servers. IMHO (and experience) doing it for Apache would be pretty useless.
Depends heavily on how you have configured Apache. If you are using something like PHP and the forking model (most common MPM configuration), you can only handle as many requests as you have workers; additionally you are spinning up a full PHP interpreter when serving static assets. In my experience[1], putting Nginx in front of Apache to serve static assets and leaving Apache as a sort of application server is one o…
This was how we did it at my last job, a state university.
Re: Nginx has replaced Apache as the most used web server among the top 10,000 sites
#34Earlier quoted context omitted.
Isn't it considered best practice to serve your static files through Nginx itself and only reverse proxy requests for dynamic endpoints? And if that's the case, Shouldn't Nginx be counted as a full web server?
You can configure Nginx to cache and serve html or as a load balancer. In these cases it isn't the "real" web server, and it's common.
I disagree. I don't care if nginx is in front of apache, varnish, or some ruby or python web server. If nginx is what serves the final request to the client, it's the webserver. Period.
edit: nginx is the last mile. You can't say everyone in the USA has access to fiber because further upstream their traffic traverses a fiber network. Their last mile is DSL/Cable/etc. When it comes to the user experience, last mile is all that counts.
Re: Nginx has replaced Apache as the most used web server among the top 10,000 sites
#35Couldn't these results be skewed because Nginx is often used as a reverse proxy? If there is Apache or something custom behind Nginx it will show up as Nginx I guess. I do not see this issue adressed and it might cause significant skew if you look at the top websites (since they will more often deploy these kinds of tricks)
You reverse because you can't have two apps on the same port, obviously...but the real reason is because apache's lack of features...and apache is bad!
Even if apache is running in the background to serve up things like php, its most likely because there is some config that hasn't been converted to run the site on something like fast-cgi or FPM.
I wonder how something like haproxy appears when nginx is behind it.
Re: Nginx has replaced Apache as the most used web server among the top 10,000 sites
#36Couldn't these results be skewed because Nginx is often used as a reverse proxy? If there is Apache or something custom behind Nginx it will show up as Nginx I guess. I do not see this issue adressed and it might cause significant skew if you look at the top websites (since they will more often deploy these kinds of tricks)
We use nginx as a load balancer on its own machine and distribute requests to a small farm of machines running windows/iis.
Nginx is great as a load balancer, not quite as sophisticated as HAProxy but the SSL support is good and it gets the job done pretty well.
I'm sure we're not the only ones.
Re: Nginx has replaced Apache as the most used web server among the top 10,000 sites
#37Earlier quoted context omitted.
wouldn't just changing the apache keep alive have been even easier than setting up a whole other web server and adding that to the mix? If the nginx keep alive was set at 15 seconds, you'd have had a similar problem, no?
No. Because Nginx doesn't dedicate a thread or process to each open connection.
Doesn't that raise security concerns?
Re: Nginx has replaced Apache as the most used web server among the top 10,000 sites
#38Earlier quoted context omitted.
You can configure Nginx to cache and serve html or as a load balancer. In these cases it isn't the "real" web server, and it's common.
I disagree. I don't care if nginx is in front of apache, varnish, or some ruby or python web server. If nginx is what serves the final request to the client, it's the webserver. Period. edit: nginx is the last mile. You can't say everyone in the USA has access to fiber because further upstream their traffic traverses a fiber network. Their last mile is DSL/Cable/etc. When it comes to the user experience, last mile is…
Sure. But it doesn't make sense to not count the other web servers involved. (Even though that's often not possible)
Re: Nginx has replaced Apache as the most used web server among the top 10,000 sites
#39Couldn't these results be skewed because Nginx is often used as a reverse proxy? If there is Apache or something custom behind Nginx it will show up as Nginx I guess. I do not see this issue adressed and it might cause significant skew if you look at the top websites (since they will more often deploy these kinds of tricks)
Nginx is used as a reverse proxy for less strong application servers. IMHO (and experience) doing it for Apache would be pretty useless.
At absolute bare minimum it allows for error mitigation for the underlying server application.
In other words, your site doesn't necessarily have to be down even if Apache is down (assuming you're for some reason bound to Apache).
Re: Nginx has replaced Apache as the most used web server among the top 10,000 sites
#40Earlier quoted context omitted.
You can configure Nginx to cache and serve html or as a load balancer. In these cases it isn't the "real" web server, and it's common.
I disagree. I don't care if nginx is in front of apache, varnish, or some ruby or python web server. If nginx is what serves the final request to the client, it's the webserver. Period. edit: nginx is the last mile. You can't say everyone in the USA has access to fiber because further upstream their traffic traverses a fiber network. Their last mile is DSL/Cable/etc. When it comes to the user experience, last mile is…
By that logic (I'm not saying the conclusion is wrong), no one has fiber because we always end up translating it to electrical pulses before hitting the cpu, and chrome is the largest webserver because it always checks its own cache before going out to the network.