Figure 1 outlines a basic three tired architecture in ASP.
The markup file defines the look and layout of the web form and the code behind file contains the presentation logic.
It’s a clean separation because both the markup and the code-behind layers house specific sets of functionality that benefit from being apart.
Designers don’t have to worry about messing up code to make user interface changes, and developers don’t have to worry about sifting through the user-interface to update code.
Building an understanding of architectural concepts is an essential aspect of managing your career.
Technical interviews normally contain a battery of questions to gauge your architectural knowledge during the hiring process, and your architectural ability only becomes more important as you ascend through the ranks.
So it’s always a good idea to make sure you have a good grasp on the fundamentals.In this article you will explore a key component of application architecture known as the Data Access Layer (DAL), which helps separate data-access logic from your business objects.The article discusses the concepts behind the DAL, and the associated PDF file takes a look at a full-blown DAL implementation.This is the first in a series of articles discussing some of the cool things you can do with a DAL, so the code and concepts in this article form the base for future discussions.Layered application designs are extremely popular because they increase application performance, scalability, flexibility, code reuse, and have a myriad of other benefits that I could rattle off if I had all of the architectural buzzwords memorized.In the classic three tier design, applications break down into three major areas of functionality: Inside each of these tiers there may also exist a series of sub-layers that provide an even more granular break up the functional areas of the application.