Differences between revisions 1 and 11 (spanning 10 versions)
Revision 1 as of 2009-11-16 16:27:06
Size: 67
Editor: fruity
Comment:
Revision 11 as of 2009-11-16 19:00:17
Size: 1092
Editor: fruity
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
==== Breaking the LAMP loop, alternative web serving methods ==== ===== Breaking the LAMP loop, alternative web serving methods =====

Lately I decided to look elsewhere than the usual "linux apache mysql php".
Reading on docs makes me draw something like apache or ngingx as a load balancer front-end, the same as the backend adding lighttpd for fast streaming ofdata.
This leave me more confused than before:
 * apache or ngingx? old but solid or new with an ongoing development? wich for load and wich for serving?


My head started to wirl and I thought myself using a beast like apache to do load balancing was a bit like killing a fly with a nuke, so for I looked elsewhere for two solutions, reverse proxy or tcp-loadbalance? and then apt-cache search came to the rescue:

[[http://www.apsis.ch/pound/|Pound]]

The config file is one placed in ''/etc/pound/pound.conf'', is very simple and straight forward.

[[/pound|Pound Reverse proxy, load balancer and HTTPS front-end for Web servers]]

For the serving of static/dynamic content I de

 * database: mysql?postgres?sqlite?ORACLE!??

[[/yaws|Yet Another Web Server(in erlang)]]

Breaking the LAMP loop, alternative web serving methods

Lately I decided to look elsewhere than the usual "linux apache mysql php". Reading on docs makes me draw something like apache or ngingx as a load balancer front-end, the same as the backend adding lighttpd for fast streaming ofdata. This leave me more confused than before:

  • apache or ngingx? old but solid or new with an ongoing development? wich for load and wich for serving?

My head started to wirl and I thought myself using a beast like apache to do load balancing was a bit like killing a fly with a nuke, so for I looked elsewhere for two solutions, reverse proxy or tcp-loadbalance? and then apt-cache search came to the rescue:

Pound

The config file is one placed in /etc/pound/pound.conf, is very simple and straight forward.

Pound Reverse proxy, load balancer and HTTPS front-end for Web servers

For the serving of static/dynamic content I de

  • database: mysql?postgres?sqlite?ORACLE!??

Yet Another Web Server(in erlang)

fruity/Web (last edited 2009-11-17 00:48:20 by fruity)