3-Tier Architecture or MVC ? Which is more appropriate for an enterprise web application.

Question

0.00/5 (No votes)

See more:

Hi,

I am planning on making a dot net web application with database in SQL Server.

I have heard about 3-Tier Architecture and MVC. Which is more appropriate to create an enterprise web application.

Requesting your valuable suggestions.

Thanks in advance

Posted 31-Oct-13 1:18am

Rahul Krishnan R

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)

Pratik Bhuva · Answer 1 · 2013-10-31T01:42:00

Well Rahul its totally depend on Your requirements.

If You Project Cost is low then i will suggest you to use Asp.Net Web Froms.Generally we should prefer it in RAD development when we don't need very long term maintanence or greater future changes.

And if the cost is not an issue and your more focus is on performance and long term maintainability & future changes then you should use MVC.

Here are some good discussion over this topics.Just look at this Your idea might be clear.

http://stackoverflow.com/questions/102558/biggest-advantage-to-using-asp-net-mvc-vs-web-forms[^]

http://stackoverflow.com/questions/5930730/how-to-decide-on-webforms-vs-asp-net-mvc-3-for-new-project[^]

http://programmers.stackexchange.com/questions/95212/when-to-favor-asp-net-webforms-over-mvc[^]

Hope This Help You.
--------------------
Pratik Bhuva

E.F. Nijboer · Answer 2 · 2013-10-31T01:42:00

3-tier and mvc are two totally different things. You might get fooled by the fact that they both separate concerns but on a completely different level. The mvc works on application level where a 3-tier architecture is on enterprise level. Your mvc web application is simply at application level of the 3-tier. The 3-tier would still have two other tiers, namely the service and database tier. The service tier is to ensure enterprise level consistency and communicates to the database tier (maybe also other services and even more). Other applications use that service tier for enterprise functionality. It makes it easier because enterprise level changes can be done at a single point (if well designed). Your mvc model is just a consumer of the service tier. The view and controller don't (shouldn't) even know about it. It is separated and handled by the model.

Hopefully this makes it somewhat more clear that your mvc is just a presentation tier (or layer). It could be easily replaced or added to a desktop version. By the way, there is also a difference between tier and layer in which a tier is a physical separation (different server) and a layer is just software separation. As is always at enterprise level, they overcomplicated it as much as possible to put up a barrier for all who is new to it all.

Good luck!

3-Tier Architecture or MVC ? Which is more appropriate for an enterprise web application.

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0