In looking for what's required fo a site, I'm trying to find
docs/overview/mentors to talk to/etc,...

Basically, I'm considering what's required in terms of
hardware/apps/functionality for each server to be able to support a
site/system of ~100,000/day

i'm considering:
 http server
 app server (single/multiple)
 db server

Is there someone I can actually talk to who's actually been involved with
the architecting/implemenation of this kind of structure.

Any really good pointers that someone can point me to to get well versed in
this area.

Thanks

-Bruce

If it's 95% "pull content from the database and display it" (eg a page
from an article), look at creating static html files which get
regenerated when the content is edited
(http://pear.php.net/packages.php?catpid=3&catname=Caching)

A webserver should handle 100k hits a day of static html pretty easily.

If you're doing complicated database queries with every page hit then
you're going to need a lot more database servers than http servers.

--
Postgresql & php tutorials
http://www.designmagick.com/

-----------------------------------------------Reply-----------------------------------------------