So what doe a truly HUGE deployment of TFS look like?


When I first started, this diagram and info was being circulated, and it was pretty darned impressive.  I thought it was appropriate to resurface it as questions about deployment scenarios has come up a lot lately.  Here are some highlights from what Microsoft's very own developer division is doing:



  • We have servers both on the intranet and the extranet.

  • There are servers and/or proxies in each of 5 different regions around the world and accessed from more places than that.  We're in the process of setting up a proxy in China right now but it wasn't in place at the time this diagram was made.

  • DevDiv - The server used by Developer Division (this is the server I publish all of my dogfood stats about).

  • MSIT - The server used by internal Microsoft IT teams.

  • MSCOM - The server for development done in the Microsoft.com organization.

  • PG Consolidated - A collection of "smaller" (generally less than 100 people) teams from around the company.

  • MSN - The server used by a collection of MSN teams (although the entire MSN org has not adopted TFS yet).

  • EVAL OFFICE - Office is currently in the process of evaluating TFS for use in developing their next release.  We set up this server for them to experiment with to help them get familiar with TFS, decide what customizations they will need to make, etc.

  • SQL - The server being used by the SQL Server team.  They are only using TFS for work item tracking right now.

  • EVAL SPCore - This is a general eval server for teams that want to try out TFS.  "SPCore" derives from the name of our internal adoption team - the Solution Provider team.  They help teams with the process of adopting TFS.

  • EVAL * - More Evaluation servers.

  • Pre-production environment - A set of virtual machines that we can use to load images of production servers to test various maintenance and upgrade procedures without putting production machines in jeopardy.

  • Monitoring - We have a set of monitoring servers that perform various tasks including measuring availability and performance of other servers and mirroring checkins and work item changes between TFS and the internal team development tools we are gradually migrating away from.

  • Extranet - a server set up for external partners who collaborate with Microsoft to use.


 Dogfood topology


Here is a link to the latest stats off of Brian Harry's blog from February 2007: http://blogs.msdn.com/bharry/archive/2007/02/08/february-devdiv-dogfood-statistics.aspx

Comments (1)

  1. Ever wondered whether your Team Foundation Server deployment is? Have a look at Angela's blog post

Skip to main content