N-Tier Data Applications Overview

Note

This article applies to Visual Studio 2015. If you're looking for Visual Studio 2017 documentation, use the version selector at the top left. We recommend upgrading to Visual Studio 2017. Download it here.

N-tier* data applications are data applications that are separated into multiple tiers. Also called "distributed applications" and "multitier applications," n-tier applications separate processing into discrete tiers that are distributed between the client and the server. When you develop applications that access data, you should have a clear separation between the various tiers that make up the application.

A typical n-tier application includes a presentation tier, a middle tier, and a data tier. The easiest way to separate the various tiers in an n-tier application is to create discrete projects for each tier that you want to include in your application. For example, the presentation tier might be a Windows Forms application, whereas the data access logic might be a class library located in the middle tier. Additionally, the presentation layer might communicate with the data access logic in the middle tier through a service such as a service. Separating application components into separate tiers increases the maintainability and scalability of the application. It does this by enabling easier adoption of new technologies that can be applied to a single tier without the requirement to redesign the whole solution. In addition, n-tier applications typically store sensitive information in the middle-tier, which maintains isolation from the presentation tier.

Visual Studio contains several features to help developers create n-tier applications:

Presentation Tier

The presentation tier is the tier in which users interact with an application. It often contains additional application logic also. Typical presentation tier components include the following:

Middle Tier

The middle tier is the layer that the presentation tier and the data tier use to communicate with each other. Typical middle tier components include the following:

  • Business logic, such as business rules and data validation.

  • Data access components and logic, such as the following:

    The following illustration shows features and technologies that are available in Visual Studio and where they might fit in to the middle tier of an n-tier application.

    Middle tier components
    Middle tier

    The middle tier typically connects to the data tier by using a data connection. This data connection is typically stored in the data access component.

Data Tier

The data tier is basically the server that stores an application's data (for example, a server running SQL Server).

The following illustration shows features and technologies that are available in Visual Studio and where they might fit in to the data tier of an n-tier application.

Data tier components
Data tier

The data tier cannot be accessed directly from the client in the presentation tier. Instead, the data access component in the middle tier is used for communication between the presentation and data tiers.

Help for N-Tier Development

The following topics provide information about working with n-tier applications:

Separate datasets and TableAdapters into different projects

Walkthrough: Creating an N-Tier Data Application

Walkthrough: Adding Validation to an N-Tier Data Application

N-Tier and Remote Applications with LINQ to SQL

See Also

Attach
Walkthrough: Creating an N-Tier Data Application
Hierarchical update
Dataset tools in Visual Studio
Accessing data in Visual Studio