is this 3-tier architecture or anything else?

Question

0.00/5 (No votes)

See more:

Here i have a little confusion because i'am new to 3-tier architecture.

iam thinking that if a webapplication(ex: asp.net empty Webapplication) have

BusinessLogicLayer(classlibrary),DataAccessLayer(classlibrary), that is called 3 tier architecture.

and iam searched in many articles in internet that they are stating that 3-tier architecture can have 1.Asp.net Web Application 2.BusinessObjects 3.BusinessLogicLayer
4.DataAccessLayer But Stil it is called 3 Tier-Architecture.

Here both are called as 3-tier architecture why?. how many projects that can be added to 3 tier architecture.

Posted 14-Dec-14 21:03pm

raxhemanth

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Kornfeld Eliyahu Peter · Answer 1 · 2014-12-14T21:14:00

You are also confused between layer and tier...
Tier is about the physical distribution of an application - meaning that different parts (like web server, DB server and so on) are located physically in different places...
Layers are about the logical split of your application - and that what you are talking about in your question.
To make it clear a multi-tier application is for sure a multi-layer too, but a multi-layer application not necessarily multi-tier too!
The proper numbering of tiers/layers are irrelevant - it can be called n-tier or 3-tier (n-layer or 3-layer) and all about the same - separation! So do not let the names (numbers) confuse you...

Sinisa Hajnal · Answer 2 · 2014-12-14T21:09:00

Solution 1

You can add as many projects as you want. Three tier nomination has nothing to do with number of projects in your solution. It represents the separation of interface classes (your views, pages, forms), business logic (the application rules and entities) and data access layer (your repository, be it database, XML or something else)

In you example above tiers would be
tier 1. Asp.net web pages
tier 2. business objects and business logic
tier 3. data access

I hope this clears the subject a bit.

Posted 14-Dec-14 21:09pm

Sinisa Hajnal

Comments

raxhemanth 15-Dec-14 3:22am

sir if i add
tier 1. Asp.net web pages
tier 2. business objects and business logic
tier 3. data access

If i add Seperate ClassLibrary as BusineessObjcets to the above solution for instance what it is called as tier or Layer.

Sinisa Hajnal 15-Dec-14 6:19am

Again, it is the meaning of the library rather then its type which determines its tier. I use tier and layer interchangeably, sorry for the confusion. Tier is "correct" word in this context. You could have custom controls library that would be part of presentation layer (tier 1) despite being DLL. The position of the projects depends on its meaning/use, not type.