Is it worth checking into a webserver apart from apache?
I've commonly released my websites under apache, merely by default. I've listened to features of NGinX though and also I'm asking yourself under which problems it would certainly transcend. Along with apache and also Nginx, what the various other alternatives are for webservers and also what are their advantages?
There are a PILE of webservers around. I anticipate relies on the use you desire. Apache will certainly do a lot of what individuals desire, it's recognized excellent, well upgraded, and also will certainly work on virtually any kind of hardware and also os mix.
For a contrast of internet servers, check Comparison of web server software.
Apache can be a little bit hefty, and also can tip over when under hefty load. There are lighter weight web servers readily available, consisting of nginx, lighttpd, and also cherokee.
These light-weight alternatives can be set up to offer fixed documents promptly, and also delegate vibrant server - side job to Apache.
Among the internet servers made use of to have a huge spike in load every couple of hrs. After checking into the logs, I figured out when the load spike took place, there where a great deal of individuals considering the gallery.
So I off - crammed 99% of the fixed web content from apache to nginx. apache was entrusted to offer every one of the php. The load on my internet servers went down to a wonderful reduced number and also without even more high load spikes.
If you are aiming to get even more out of your web servers, most definitely have some light - weight server offer all the fixed web content.
Netcraft tracks market share of internet servers & according to them, IIS stands 2nd after Apache with a 26.03% share (since July 2010). This is based upon a study of 205+million websites
This link has reasons that you need to look into IIS7 if you make use of Apache today
It actually relies on what you're doing.
If you just have fixed web content, you do not require Apache. nginx or lighttpd would certainly offer you simply penalty.
If you have a mix of fixed and also vibrant (well, Perl or PHP), yet a tiny website, you can still manage with among those different plus FastCGI, or simply toss the entire point right into Apache.
If you're offering Ruby in addition to your fixed web content,
mod_passenger in Apache need to offer you well, with nginx/lighttpd/etc offering your fixed web content.
For Python (my location of experience), you can have Apache make use of
mod_python if you desire yet plan for sluggishness.
mod_wsgi is much better yet you still have the expenses of Apache, which is great if you have a great deal of hefty vibrant website traffic. Apache is a hefty lifter a lot of the moment.
If you do not have a lots of rush hour, check into new systems like
uWSGI or the all - in - one server Cherokee to manage your Python. Cherokee takes care of fixed documents, also. The remainder, you'll still intend to make use of nginx/lighttpd to offer the fixed web content.
Java and also various other languages, I have no suggestion concerning.
The wonderful feature of making use of nginx, however, is that it's extremely configurable. So set up a number of fixed web servers with various subdomains, one each for CSS, photos, and also JS. In this way you aid stay clear of the restriction of 2 documents per domain name at once. Set up numerous web servers and afterwards set up an nginx proxy/load - balancer before them to see to it every one of your fixed web content is constantly readily available.
Basicaly, YES, consider greater than simply Apache!