Three tier architecture in ASP.NET

Just now I’m learning and building a project based on three tier architecture.
This is extremely useful especially when you’re going to build an application that would be solid, hacker-proof and could be extended in future.
The first tier is Presentation. This will be viewed and used by the end user. Like you view a web page, perticipate etc.
The second tier is Business tier. It plays the role of a bridge between upper and lower tier. In the lower tier there is Data tier. Business tier stays between them, ie; Presentation and Data, maintaining the connection.
How this happens I’ll explain.
Being a developer, in the one hand you might have many end users. The number of end users are varying. It could be very large. So you have to build a site that’d sustain that pressure and will not be broken.
On the other hand you have your client. They could be also very demanding. Moreover, lately after a site has been built up, client might want to extend the application.
So the Business tier, where client will operate, should be flexible. To maintain that flexibility, you write down your own classes that will have thier own members. This classes could be static. There could be struct for maintaining speed. You know struct is mainly used as data container. Speed is a factor in a dynamic site.
In the lower section, there is the final tier Data. It is called Data tier or Database tier. The valuable data resides in Data tier.
The whole architecture goes in a sequential flow so that from the Presentation tier you can not jump onto the Data tier. The Businaess tier not only stands between them but also guards the Data tier controlling the end user’s demand and query against the Data.
Altogether, the whole three tier architecture not only looks impregnable but also stands solid against any malicious codes.
It looks like this:
1) Presentation tier
=>
2) Business tier
=>
3) Data tier
=>
2) Business tier
=>
1) Presentation tier
The flow moves down and goes up accordingly.
A note for the beginners like me: the Object Oriented Programming solidly displays its main characteristics in the Business tier where you write down the classes like Generic Data Access, Database Access, many utility classes like sending mails etc.
In your classes you can call the default .NET classes accordingly, create their instances and use them.
At the end of the day the application is ready, dynamic and kicking.
Best of luck!

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s