MVC benefits over n-tiers architecture
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!
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
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.
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Join our community and discover your potential
Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.
*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.