Practical mod_perl / HTML Book /



previous page: 5.8.2.1. The server cluster
  
page up: HTML Version of the book
  
next page: 5.8.2.2.1. Upgrading live server components by swapping machines

5.8.2.2. The single server


It's not uncommon for a popular web site to run on a single machine. It's also common for a web site to run on multiple machines, with one machine dedicated to serving static objects (such as images and static HTML files), another serving dynamically generated responses, and perhaps even a third machine that acts as a dedicated database server.

Therefore, the situation that must be addressed is where just one machine runs the service or where the service is spread over a few machines, with each performing a unique task, such that no machine can be shut down even for a single minute, and leaving the service unavailable for more than five seconds is unacceptable. In this case, two different tasks may be required: upgrading the software on the server (including the Apache server), and upgrading the code of the service itself (i.e., custom modules and scripts).

 

Continue to:

  • prev: 5.8.2.1. The server cluster
  • Table of Contents
  • next: 5.8.2.2.1. Upgrading live server components by swapping machines







TOP
previous page: 5.8.2.1. The server cluster
  
page up: HTML Version of the book
  
next page: 5.8.2.2.1. Upgrading live server components by swapping machines


Menu

  • HTML Book
  • PDF Book
  • Download Code
  • Table of Contents
  • Errata
  • mod_perl2 User's Guide
  • Sitemap

Search


Add to Google




Creative Commons License


Written by
Eric Cholet (Logilune) and
Stas Bekman (StasoSphere & Free Books).


[ Privacy Policy | Terms of Use | About Us | Search ]

© 2007 StasoSphere.com