Asp.net| Program | design | Data designing and implementing a versatile data access tier for a asp.net
by Paul Abarham
In this article, we'll drill down deeper the "a n-tier architecture and our focus'll be" on the data ACC ESS Tier (DAT)
Abstract
Design and implement a general-purpose data access layer application for ASP.net
Author Paul Abarham translation cwxiao888@163.com
In this article, we'll delve into the design of the n-tier architecture, and we'll focus on DAT (Dat,data access tier).
Summary
In this article, we'll drill down deeper the "a n-tier architecture and our focus'll be" on the data ACC ESS Tier (DAT) (Figure 0). Our goal are to design and implement a appropriate data access tier (DAT) for scalable, reliable and interoperable web appl Ication. I have divided this article in to two major parts. In the "I", we'll discuss about architectural goals, typed DataSet, Eventlogs and httpmodules, which are To understand the second part of this article. We'll build in the second part a small (but fine) n-tier application and my focus'll be on design and implementation O F data access tier. You need a SQL Server (Database:northwind) and vs.net to follow this article.
In this article, we will delve into the design of the n-tier architecture, and we will focus on DAT (Dat,data access tier) (Figure 0). Our goal is to design and implement a scalable, reliable and mutually cooperative DAT network application. I have divided this article into two main sections. In the first part, we will discuss the purpose of architecture, typed Dataset,eventlogs and httpmodules, which is beneficial to understanding the second part of this article. In the second section we will create a small (but very good) n-tier, and our focus is on designing and implementing DAT. You need a SQL Server (database: Northwind) and vs.net to follow this article.
Contents: Content
1. Designing Goals of a data access tier (DAT) DAT design goal
1.1 Architectural Goals Architectural objectives
Installation of the 1.2 installation of the prototype prototype
1.3 Typed Datasets
1.4 Event Logs
1.5 httpmodules
2.0 implementing versatile data access tier (DAT) implements common dat
2.1 Implemeting a super class for data access tier. Implement a superclass for DAT (super Class)
2.2 A performance test to evaluate SqlDataReader and datasets objects in the business tier.
Evaluate performance tests for SqlDataReader and DataSet objects in the business layer (business tier)
2.3 Can I extend this data access tier (DAT) to access multi-databases.
How can I extend this dat to access multi-tier databases (Access multi-databases)
2.4 How can I apply the database transactions with different isolation level?
How do I apply database processing (DB transactions) with different isolation levels (different isolation level)?
2.5 How can I insert and retrieve images?
How do I insert and retrieve images?
Figure 0 shows us a typical 3 Tier application this is dissected into to three major disjunctive-layers, which are data Tier (DA), middle tier and presentation tier (PT).
Figure 0 shows us a typical 3 tier application, which is divided into three main separation layers, data tier (DA), middle tier and presentation tier (PT).
If you are are not familiar with N-tier architecture, I like to recommend following.
Http://www.c-sharpcorner.com/Tutorials/Building3TierAppPA.asp
Http://www.c-sharpcorner.com/Code/2002/June/AdoNetWinDNAPerspective.asp
If you are not familiar with the N-tier architecture, I recommend the following articles to you.
Http://www.c-sharpcorner.com/Tutorials/Building3TierAppPA.asp
Http://www.c-sharpcorner.com/Code/2002/June/AdoNetWinDNAPerspective.asp
1. Designing an appropriate data access tier (DAT)
1.0 Architectural Goals
The must requirements of a enterprise application can be expressed through the following buzzwords
Interoperability and Extendibility
Scalability and performance
Reliability and Manageability
Security
Let us look some of the "buzzwords closer, what do they really?"
Interoperability deals with the ability of a system to communicate with other internal or external systems in a Heterogene ous environment. This is a very important issue, because we need information to act just in time to meet needs of my our customers and busines S. To achieve this important goal, we system must able to offer and consume Web services.
To being agile in your business, sometimes your need to extend your. If we couple a system so tightly to the systems, then it may trigger a "modify avalanche" e.g Application via email, which represents data tables through comma separated. The recipient'll open the email and parse it to gain information. Say, if we want add or change a column, then we have to modify other depending systems too the order of because HA ve changed). In order to avoid "modify avalanches", we must couple systems the using loosely technologies like WEB services (such Y:xml supported Technologies).
Scalability is a MEAs
