Differences between revisions 6 and 8 (spanning 2 versions)
Revision 6 as of 2009-11-16 16:40:18
Size: 834
Editor: fruity
Comment:
Revision 8 as of 2009-11-16 16:40:41
Size: 832
Editor: fruity
Comment:
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
    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:
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:

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?

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:

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

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

Yet Another Web Server(in erlang)

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