Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

when the traffic for a website grows i dont think one apache server in a vps is the way to go. i would like to know more about how i then should set up the server side architecture.

im not that much into hardware stuff (what kind of cables to use, different cpu architectures etc), but interested in the software architecture:

  • what servers (apache, nginx, squid, varnish etc) to use and how they interact with each other
  • one server in one machine?
  • how many mysql servers.
  • how many apache, nginx servers and so on.
  • how the "machine court" looks like.

are there any good books about this area?

share|improve this question
up vote 3 down vote accepted

Not really a book though.

This site tries to bring together all the lore, art, science, practice, and experience of building scalable websites into one place so you can learn how to build your website with confidence.

You can read about youtube, google, plenty of fish architecture.

share|improve this answer
what a good resource! far better than any book i guess, cause its real practice and not just theoretical. – ajsie Apr 5 '10 at 10:03

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.