Layered vs Tiered Architecture in asp.net

Question

1.00/5 (1 vote)

See more:

Hello Friend
I am newbie to asp.net and now I am creating a Project where i have a requirement to use Tiered Architecture.
To do so i have created Class Libraries for Buissness Layer Data Acces Logic and Entity Library and finally my web application
All the above stuff i have in single solution. Now when it comes to deployment i've Application server and Database Server.
But after doing some RND I came to know that these Layers are Logical Sepration and When we deploy those on different Server then we can call it as Layered Architecture,But Practically i've single Application Server in that case we can call it as Layered Architecture
Correct me if I am Wrong.
So how to achieve Tiered Architecture using single physical machine(server)

Posted 18-Mar-13 5:25am

Rakesh S S

Updated 18-Mar-13 20:43pm

v3

Add a Solution

Comments

Sergey Alexandrovich Kryukov 18-Mar-13 12:29pm

The alternative is not clear. A tier also normally plays a role of a kind of a layer. If you want to make a choice, that choice can be between tiers and — what?
And decisions depend on the goals and character of your project, which you did not really share with us...
—SA

Rakesh S S 18-Mar-13 13:08pm

I want to make application with Tiered Architecture with single Application Server.
I've Just Created those Layer as mentioned

CHill60 18-Mar-13 13:25pm

You could try implementing the data access layer (aka tier) as a web service - that would enable a physical separation of the layers as well as the logical separation?

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)