Before diving into the technologies that support a web farm, it's important to understand some high-level concepts for configuring the content for a web farm and to know which method you will use.
There are essentially three web farm file content configurations:
The solution that you choose will often be based on the project requirements, budget, your previous experience, and/or available hardware. Each solution has its own set of advantages and limitations.
Figure 16.8 shows a web farm configuration using local content. Each of the web servers keeps the content locally, and therefore it's up to the system administrator to set up either an automatic method of replication or a way to push content to all nodes after it has gone through the quality assurance team and is ready for deployment. In the case of the website writing files or changes to disk, it's important that the content be immediately replicated to the other servers so that they remain in sync.
There are several advantages and disadvantages of a web farm file content configuration using local content. Following are some advantages: