as stated above MVC can be a used in 2 or 3 tier architectures depending on the model. MVC is an old pattern used for the presentation. The mac api has used it for years, java has had swing for web apps, and is common in multi-threaded applications.
the main tenant of MVC is the view sends commands (messages) to the controller, the controller updates the model, the model sends update messages to the view. Because web apps are client request/server response, the view send to the controller, and the model
update of the view are combined into one request, as the model can not send update messages to the view. in the web world, a new view is produced.
if you do a 3 tier mvc app now days, there are a lot more layers. you may business layer and data access in the business model, and you may have view models that talk to the business models. the view models have view and navigation rules rather than business
rules.
bruce (sqlwo...
All-Star
36736 Points
5438 Posts
Re: MVC V.S N-Tier Architecture
Mar 23, 2011 03:36 PM|LINK
as stated above MVC can be a used in 2 or 3 tier architectures depending on the model. MVC is an old pattern used for the presentation. The mac api has used it for years, java has had swing for web apps, and is common in multi-threaded applications.
the main tenant of MVC is the view sends commands (messages) to the controller, the controller updates the model, the model sends update messages to the view. Because web apps are client request/server response, the view send to the controller, and the model update of the view are combined into one request, as the model can not send update messages to the view. in the web world, a new view is produced.
if you do a 3 tier mvc app now days, there are a lot more layers. you may business layer and data access in the business model, and you may have view models that talk to the business models. the view models have view and navigation rules rather than business rules.