Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!
Learn how Concerto can help you.
Solved
MVC benefits over n-tiers architecture
Posted on 2008-10-05
Hi Experts!!
I'm just starting a new web application and somebody told me to use the ASP.net MVC.
After few search over the internet I can't find any benefits over using the MVC instead of a n-tiers architectures (presentation, property, business, db).
Should I use the MVC framework/pattern .. or continue the development process using a standard n-tiers architecture?
I've read those article
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=891283&SiteID=1
http://msdn.microsoft.com/en-us/magazine/cc337884.aspx
Thanks!
I'm just starting a new web application and somebody told me to use the ASP.net MVC.
After few search over the internet I can't find any benefits over using the MVC instead of a n-tiers architectures (presentation, property, business, db).
Should I use the MVC framework/pattern .. or continue the development process using a standard n-tiers architecture?
I've read those article
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=891283&SiteID=1
http://msdn.microsoft.com/en-us/magazine/cc337884.aspx
Thanks!
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
3 Comments
HI
n-tier is an architecture that helps you to develop distributed applications, the main advantage of using that is scalability.
The MVC is a design pattern, it helps you implement n-tier architecture in a way that insures that tiers are not tightly coupled.
What MVC says is that only your controller (Business Logic) should access the Model (generally DB) while the view access data using the Controller API without being aware to the source of the data. That implies that a change in the database will affect the Controller but not the View (GUI) since the interface between the Controller and the View should not change.
So, those terms a complete each other and are not contradictory.
n-tier is an architecture that helps you to develop distributed applications, the main advantage of using that is scalability.
The MVC is a design pattern, it helps you implement n-tier architecture in a way that insures that tiers are not tightly coupled.
What MVC says is that only your controller (Business Logic) should access the Model (generally DB) while the view access data using the Controller API without being aware to the source of the data. That implies that a change in the database will affect the Controller but not the View (GUI) since the interface between the Controller and the View should not change.
So, those terms a complete each other and are not contradictory.
Ok, so basically their is no really needs to implement the MVC in therm of performance even if we plan to have thousand of simultaneous users on our webapp.
HI
Again, you will want to implement the MVC design pattern in order to get a well n-tier application. It worths the effort since each change in the life-cycle of your application is remarkably more simple when you use patterns.
When using asp.net
You asp page is the view
You should have a set of DLLs that implement your application logic, you can wrap the BL functionality as a set of WCF services if you want, that will give you location transparency (you can run your services on separate machines) and scalability.
You should have a Data Access Layer library that handles your model , you can use MS Enterprise library to auto generate code that handles your data for you , or you can use LINQ , in that case you should have to write the DAL by yourself.
Again, you will want to implement the MVC design pattern in order to get a well n-tier application. It worths the effort since each change in the life-cycle of your application is remarkably more simple when you use patterns.
When using asp.net
You asp page is the view
You should have a set of DLLs that implement your application logic, you can wrap the BL functionality as a set of WCF services if you want, that will give you location transparency (you can run your services on separate machines) and scalability.
You should have a Data Access Layer library that handles your model , you can use MS Enterprise library to auto generate code that handles your data for you , or you can use LINQ , in that case you should have to write the DAL by yourself.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
A long time ago (May 2011), I have written an article showing you how to create a DLL using Visual Studio 2005 to be hosted in SQL Server 2005. That was valid at that time and it is still valid if you are still using these versions. You can still re…
It was really hard time for me to get the understanding of Delegates in C#. I went through many websites and articles but I found them very clumsy. After going through those sites, I noted down the points in a easy way so here I am sharing that unde…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster.
To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…
Suggested Courses
Course of the Month8 days, 9 hours left to enroll
721 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.