WHAT'S IN THIS CHAPTER?
Understanding architectural changes
Understanding scale limitations
Exploring availability solutions
Exploring load balancing
Getting to know configuration best practices
Scalability and high availability are very involved topics, and a whole book could be written on each of them. Every Team Foundation Server environment is unique, and every organization has a different usage pattern and availability requirements.
It's not the purpose or intent of this chapter to provide prescriptive guidance on exact configurations to support your environment or usage pattern. Rather, this chapter is intended to give you insight into the different factors that affect scalability, and to offer some solutions to consider in your overall environment design.
If you need advice specifically tailored to your organization's needs, your best option is to contact Microsoft Support or a Microsoft Certified Partner in your area. These people have deep knowledge and ample hands-on experience to best meet your needs.
Team Foundation Server 2010 introduced some significant architecture and infrastructure changes. On the product team, these product changes were referred to as Enterprise TFS Management (ETM). It was a significant and necessary investment of effort to allow the product to handle the future scale demands of enterprises and the Internet.
The introduction of team project collections was perhaps ...