NGINX Might Be Included With Ubuntu Server ISOs
Phoronix: NGINX Might Be Included With Ubuntu Server ISOs
While Apache is the predominant open-source web-server software currently used by Linux systems, including Ubuntu, NGINX continues to rise in popularity. NGINX continues its push with high performance while having a smaller memory footprint and carrying a BSD license. The NGINX server might be included in future releases of the Ubuntu Server and part of the Ubuntu "main" repository...
I use the Hiawatha web server myself. Not sure if it's adequate for commercial applications, but fine for a standalone home system. I just use it to test my own web site.
If you aren't connecting Hiawatha to the web, you can configure it to be inaccessible to the big bad Internet. Just edit file /etc/hiawatha.conf and uncomment the line that says:
# Interface = 127.0.0.1
Somewhat related to this topic, it might interest a lot of readers here that there is a serious vulnerability issue that is hitting Linux sites running apache, nginx and lighttpd:
If you're actually running a server connected to the outside world, I think at a minimum you ought to be running selinux as well. Not 100% sure that would protect the server, but probably would, at least from what I'm reading. This particular vulnerability is not yet fully understood.
I like Cherokee, myself. It's a decent little server, and has a nice configuration interface. Can be a little confusing to set up for certain things, but there are helpful tutorials, if you need them. It was sufficient for my tinkering at home, at least.
Nginx is a great server for sure.
As for me, I enjoy by using Nginx on my servers. Why?
1) Absolutely great at serving static files! After one guy has replaced apache with nginx on his server, I was able to notice speed increase in page load by naked eye. That's because it has been mostly static page. So there was quite a reasonable speedup I can see with naked eye. I have a fast connection. So page no longer has been "loading". It has been literally "shot" into my browser. Quite an impressive effect.
2) Lower resources usage. It's enough to have cheap microserver/VPS/... to serve quite a lot of stuff. OTOH apache is resource hog and without expensive and powerful server it performs really bad. So apache maybe not so bad for some large corporation who can afford large server farm but it really suxx for anyone on tighter budgets or those who needs more speed. You see, top busiest sites ARE using nginx for a reason. And reason is simple: they can buy far less servers than they have to if they about to handle same load levels with Apache.
3) As for me, I like Nginx config format more than Apache. Also no stupid .htaccess crap. So no moron extra disk seeks for each and every file server is serving. Maybe not a large prob on SSD but really kills Apache performance once more on mechanic HDDs.
4) Nginx haves really cool caching system. In many cases you can serve static version of page from cache instead of starting PHP for each and every request. Why re-generate the very same page 1000 times a second if the result is known to be same all the time? And I already told nginx is great at serving static.
5) Latest versions have some uber-modern features like SPDY and websockets. Something you would really expect from leading server software in year 2013, isn't it?
6) It's both decent front-end, static uploader and load balancer. It can work as standalone fully featured server, running both PHP and whatever else can use fastcgi/scgi/wsgi/... - it's really nice in smaller installations when server could be both "app server" and "frontend". In larger installations it could do load balance without suffering performance prob's.
In fact, if you're not dumb, you can easily withstand a serious slashdot effect even on cheap/weak hardware in many cases. As for me, it has got it's popularity on top busiest sites just because it really deserves it. A really decent masterpiece of software.
It haves some couple of disadvantages.
1) No dynamic modules loading. Those who needs it could try to look on Tengine, fork of nginx server made by popular chinese Taobao portal. It's a bit lagging behind in terms of versions and features though.
2) It's devs have quite specific preferences and views.
Last edited by 0xBADCODE; 05-29-2013 at 12:48 AM.
Ngninx users have sure been eager to promote it. Sometimes almost too much, I'd say.
It's easy to sell to an Apache user, but for a lighttpd guy like me - meh, show me some impressive unbiased test results and I'll consider.
Lighttpd is a worth mention, sure. I even used it for some time for myself. Though obvious disadvantages compared to nginx are:
Originally Posted by SevenOfMine
1) It can't scale as well as nginx on multiple CPUs. Nginx could launch several workers. Each worker still remains lightweight state machine (just like lighttpd is and unlike apache workers) but then OS could spread them over different CPUs. Lighttpd internally uses some threads but at least (release-quality 1.4) can't scale well in this regard. Though this only matters for really busy sites.
2) It haves worse flaw. Lighttpd have to cache WHOLE backend response. So if your backend have to upload something large or script has gone mad, lighttpd could consume non-trivial amounts of RAM (equals to response size) and would not return RAM to OS even when request has been served. This is known design issue and will not be not fixed in 1.4.x series.
3) To make it even more "funny", lighttpd 1.5.x development appears to be completely stuck/abandoned. And lighttpd 2.x not seems to be released anyhow soon. Furthermore, lighty devs have gone mad and dare to require some Gnome parts (glib) on server for 2.x. Kinda weird dependencies for server software, doh. Nginx lacks all those issues and does not needs gnome parts on server...
Conclusion: major trouble of lighttpd is crappy project management. It's handled by some students and they're not a great PMs at all. So they were #3 with only apache and IIS on top some time before. But thanks to their crappy project management they were outrun by nginx. You see, I need to serve stuff today and it's not like if I could wait for years when such major design flaw as mentioned in 2) will be fixed. Nginx project handling is much better. At least those guys are well aware of what is "production server" and what "dos" and "donts" apply and able to deal with serious issues in more or less timely fashion. Not something lighttpd team could afford. As "bonus", lighty lacks really cool cache system nginx haves. Otherwise it's not so bad server. I used it for some time but then I got some server out of RAM due to runaway script. After reading bug tracker I figured out it will literally take some years or undefined time to get it fixed. OTOH nginx does not attempts to cache whole backend response and rather passes whatever is ready to client. Which is much smarter approach and works better in various situations.
Last edited by 0xBADCODE; 05-29-2013 at 02:13 AM.