==== 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 a solution and 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 decided that also for serving apache wasn't good enough, I looked over webrick and was not stable enough, I looked over python-wisted and it wasn't fast enough and so I found [[http://yaws.hyber.org/|YAWS (Yet Another Web Server)]] written in erlang designed for performance and scalability over multiple servers.

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

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

  I need to have the vastest gamma of databases, I want to be able to store certain data to certain databases and I want to be able to do certain query over different databases.
  For this to work there is a huge amount of changes to be done in software but yet so far there is [[http://www.sqlalchemy.org/|SQLAlchemy]] and [[http://code.nytimes.com/projects/dbslayer|DBSlayer]]. I will investigate databases soon enough.

==== Wikis ====

[[/MoinMoinFarmingApache2WSGI|MoinMoin farm]]

=== FrameWorks ===

[[/django|Django notes]]