
302
CHAPTER 10 Building ScalaBle applicationS inSharepoint
All too often SharePoint farms are overbuilt, resulting in unnecessary licensing and operating costs.
Two powerful web frontends can easily host a few thousand concurrent users in a typical collaboration
environment, and potentially many more users in a properly optimized publishing environment.
Load-Balancing Options
Load-balancing your web frontends is possible because the HTTP protocol is stateless, meaning that
information is generally not persisted on the server between postbacks. Consequently, a sequence of
requests can be handled by multiple, different web frontend servers available within your SharePoint
farm. Each web frontend shares the same state and data as the other web frontends, with the exception
that different data may be cached in memory depending on what distinct pieces of data each frontend
has previously retrieved. This picture gets a bit fuzzier when session state is turned on, which requires
either sticky sessions or centralized storage of session data. Regardless, any data that can be altered
through the web frontend servers must reside within the databases, each of which acts as the single
point of storage for the data contained within. This means that for a single database, there is no possi-
bility of load balancing. Only failover clusters are possible.
Also, though application servers are i ...