Wondering the pros and cons for MVC architecture in terms of web application development? And What is the difference between MVC and 3-tire architecture?
Those are concepts but what is the benefit and what is the disadvantage by using MVC model?
Simon Guo
2010-04-20 14:44:10
@Simon Guo: Well, once you understand the concepts, you will come to know about benefits and disadvantages...To put it simply MVC allows you to separate business and presentation logic. Something cool to go for really :)
Sarfraz
2010-04-20 14:45:38
A:
As stated by @Sarfraz Wikipedia is a good starting point for this type of question.
To answer your specific question about the difference between MVC and 3-tier architecture, you need to first understand that MVC is (primarily) a GUI/User-Interface framework and design pattern.
In other words, MVC would be just one tier in your 3-tier architecture, you would still have a "service/business logic" tier and a "persistance/database" tier.
Nate Bross
2010-04-20 14:42:31
I just read from some where:Pro: the ability to have multiple views that rely upon a single model; same components can be used and called for use with any interface; model is self-contained and separate from the controller and the view, it is much less painful to change your data layer or business rules; presented with a number of reusable building blocks in the model and the view.Con: have to spend a good amount of the time thinking about the way the parts of app will interact; more files to manage than you would otherwise; overkill for small applications.
Simon Guo
2010-04-20 20:47:55
Yes, that supports my answer, that `MVC` would only be a single tier in your multi-tier architecture.
Nate Bross
2010-04-20 22:11:59