Discuss high traffic and HA development

This message is crossposted to the Back-End developers and phpSlash 
developers.

I'd like to get an IRC discussion going on what developments need to be 
done to make BE/PSL more scalable and easier to deploy in a larger 
website installation.

While I'm not saying we should get away from the easy to install, easy 
to deploy on a hosted account ideas, there is also a need for being able 
to use the code on sites serving lots of page views from multiple servers.

I'd like to do this on IRC to get more of a real time discussion going. 
  Is there a good time for everyone?  But I'm not opposed to discussion 
here as well.

This may seem a little soon in the next phpSlash release cycle for this 
discussion, but after this is done, I'd like to get another discussion 
on a more general roadmap for BE and PSL.

A couple of my ideas to throw out:

High Traffic Discussion

- Load Balancing front end
- db clustering, master/slave, read servers and write servers, etc.
- memcache support in db reads, writes, html cacheing, etc.
- static file writing to support staging, pushing to multiple servers, 
ease of serving, speed, etc.
- squid reverse proxy front end.
- Ian's block cacheing
- using a separate image server with thttpd or somebody like akamai

Joe



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php