Team Foundation Server (TFS) Architecture
Team Foundation Server Logically works in 3-tier architecture that includes client tier, the application tier and the data tier.
http://2.bp.blogspot.com/-9PByLlxii7E/UHlEFvTbk9I/AAAAAAAAARo/aqZaoUp6teU/s320/TFS+Arch.gif
Client Tier :
Client tier communicates with application tier for creating and managing projects and access project’s items. In this tier TFS has no user interface it exposes web services to use applications (like Visual Studio Team System (VSTS) ) to use TFS as data storage or dedicated TFS management applications like Team Foundation Client (TFC).
Components of client tier:
- Team Foundation Server object model.
- Visual Studio Industry Partners (VSIP) components.
- Microsoft Office integration.
- Command-line tools.
- Check-in policy framework.
Application Tier:
Application tier contain ASP.NET Web services which are not integrated by third party but can be accessible by client tier they are groped as below:
Team Foundation Data Services has following service
- Version Control Web service.
- Work Item Tracking Web service.
- Team Foundation Build Web service.
Team Foundation Integration Services has following service
- Registration Web service.
- Security Web service.
- Linking Web service.
- Eventing Web service.
- Classification Web service.
Data Tier
TFS does not support direct access to data stored on the data tier from client applications.
Instead, all requests for data must be made through the Web services on the application
tier. The TFS data tier consists of the following data stores corresponding to data services
on the application tier.
- Work item tracking.
- Version control.
- Team Foundation Build
- Reporting warehouse.