APACHE: Heavyweith/Peso Pesado

Apache is at the core of the L.A.M.P. technology stack upon which a lot of server architecture is based: Linux, Apache, MySQL, PHP; so many use L.A.M.P. as a foundation. Among them are CMSs as Drupal or WordPress; and Apache modules enable you to easily incorporate additional functionalities. For windozers or novice developers.

In general, neither Apache nor IIS are lightweight or fast. If you want the maximum number of Web pages, static or dynamic, served in the fastest possible time with the minimum of resources, you need to look beyond the big two.

NIGNX vs LIGHTTPD: eficientes

Nginx is an Web server that includes an Reverse Proxy, an Internet Message Access Protocol (IMAP) and Post Office Protocol (POP) server. The single most important reason why companies use Nginx is that its asynchronous architecture gives it a small memory footprint and low resource consumption. Nginx is asynchronous event-based, so it doesn't spawn new processes or threads for each Web page request: even as the load increases, memory use remains predictable; so can take a lot of beating from users highly efficiently.

Lighttpd, pronounced "lightly" powers such sites as some Google services (speciallyYouTube) and Wikipedia. That's taking many about. Focused on keep alive the contract between server and client one stabliced. Uses an event-driven architecture optimized for a large number of parallel connections (keep-alive) which is important for high performance Ajax applications. The good choose for Web sites that use the Ajax Web application design model and Web 2.0 apps (such Wordpress, Joomla) with high demand of request for dinamic contents that becomes static one generated. Its high dificulty for configuring if u dont know what u doin.

HIAWATHA: Segurity and performance/Seguridad y rendimiento

The real concern is running a secure Web site: so the Hiawatha Web server. Comes along with own balanced fast-cgi engine for php server, build in reverse proxy and cached keep-alive conectios, prepared for the secure Banshee PHP Web site framework, and a Hiawatha Monitor with build in web request firewall. Most security: where HTTPS used, rather than use the sometimes broken OpenSSL for Secure Socket Layer (SSL) connections, Hiawatha uses the historically high secure PolarSSL.

Conclusiones

Small businesses: the obvious choice is not to waste time on maintenance and safety , sleeping so calm and concentrate on other things and not on the website, so hiawatha is recommended. If the company level, or nonpersonal services offers dynamic content with high scalability is recommended lighttpd.

Corporations : a single web server software is not recommended when you have multiple services, best is delegated all services by finnality. Lower demand services but sensitive information: hiawatha is the choice. And for high demand services but trivial information: lighttpd is the choice. Combining the two in each section which is better, the corporate intranet is served efficiently.

Developer : due the issue here is to finish the order, and like most frameworks are for apache and nignx, would be recommended; but when deploying to production is another matter, so lighttpd is something to consider if the result relies on scalability respect performance and compatibility.

General use: The obvious choice is given lighttpd is more compatible with most frameworks , and offers most of the features that are already in nignx apache. Besides having a humble consumer .

Newbie: nignx or apache due will not have the capacity or habilities like the champions does for use lighttpd or hiawatha .

In order of suggestions taken in consideration all features and performance, event the security: