Why Use 3-tier On .Net

Question

1.00/5 (2 votes)

See more:

I'm Developer from 2 years .I never Use 3 tier architecture In .net.Is it Required to learn 3 tier architecture for future use.Or It's Old Technology. Basically I'm Used EntityFramework and dataset.One More Thing Why We Use Stored Procedure.I'm Work with two major MNC Project's In Past .But I never required to Use Stored Procedure.

Posted 29-Aug-14 4:44am

vishal2cool089

Add a Solution

2 solutions

Solution 2

"Old" or "new" is totally irrelevant. Technology can be suitable or not, outdated or not; some new technology can be outdated (there are cases when technology is outdated even at the moment when it it presented to the market), and some old technologies are absolutely actual at this moment and will be actual for a long time.

Now, the number "3" in the term 3-tier is not a world constant, is not a law of nature. It is not a technology at all. It's just that in very many setting 3 tiers present suitable architecture. You cannot even "learn 3-tier architecture". You can learn related architectural solution, but more importantly, you need to learn technological components used to make and link the tiers in general. You should always come from the goals of the application system. If 3 tiers are not enough, create 4. If 2 is enough, create 2.

—SA

Posted 29-Aug-14 7:44am

Sergey Alexandrovich Kryukov

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)

OriginalGriff · Accepted Answer · 2014-08-29T05:19:00

Three tier isn't old technology, or new technology: it's a development methodology which encourages us to separate concerns into logical groups: User interface, business logic and back end storage. And the idea is that the separation means we can reuse or replace sections when improvements are needed.

For example, you could start with a single user Access database, and upgrade to a multiuser SQL DB without changing the UI or BL.
Or you could rewrite the UI for a web application instead of Winforms without affecting the BL or DB.

It's not required, but it is a sensible approach for many tasks, and can improve reliability as it more strictly formalises the interface between modules.

Stored Procedures are not everyone's cup of tea: some don't use them at all, some use them for everything: I prefer to think I have a "sensible middle ground" where tasks which are better handled completely within the DB are done there so that the actual DB organisation doesn't have to be exposed - even to the Data Access Layer. That doesn't mean that SP's can replace a DAL - but they can complement it, reducing bandwidth usage and improving reliability and performance if used correctly.
But just like pretty much anything else, they can turn a nice simple system into a gawd-awful mess if used badly.