MVC vs MVP vs MVVM

MVC vs MVP vs MVVM

MVC

MVC是最早也是最为人所知道的分层架构模式，主要的层级特点是:

1. The model is responsible for managing the data of the application. It receives user input from the controller.
2. The view renders presentation of the model in a particular format.
3. The controller responds to the user input and performs interactions on the data model objects. The controller receives the input, optionally validates it and then passes the input to the model.

MVP

MVP是MVC上发展出来的模式，主要的层级特点是:

1. The model is an interface defining the data to be displayed or otherwise acted upon in the user interface.
2. The view is a passive interface that displays data (the model) and routes user commands (events) to the presenter to act upon that data.
3. The presenter acts upon the model and the view. It retrieves data from repositories (the model), and formats it for display in the view.

我理解它与MVC不同的主要是关注点不同，MVP的展现逻辑更重，所以不再单独由View来控制，而是将视图逻辑放在了Presenter。这种模式更偏向后台View逻辑。

MVVM(Model–view–viewmodel)

MVVM是最近几年才出来的，主要的层级特点是:

1. Model refers either to a domain model, which represents real state content (an object-oriented approach), or to the data access layer, which represents content (a data-centric approach)

2. View As in the model–view–controller (MVC) and model–view–presenter (MVP) patterns, the view is the structure, layout, and appearance of what a user sees on the screen.[7] It displays a representation of the model and receives the user’s interaction with the view (mouse clicks, keyboard input, screen tap gestures, etc.), and it forwards the handling of these to the view model via the data binding (properties, event callbacks, etc.) that is defined to link the view and view model.

3. View model The view model is an abstraction of the view exposing public properties and commands. Instead of the controller of the MVC pattern, or the presenter of the MVP pattern, MVVM has a binder, which automates communication between the view and its bound properties in the view model. The view model has been described as a state of the data in the model.[8]

   The main difference between the view model and the Presenter in the MVP pattern is that the presenter has a reference to a view, whereas the view model does not. Instead, a view directly binds to properties on the view model to send and receive updates. To function efficiently, this requires a binding technology or generating boilerplate code to do the binding

主要是对视图层增加双向绑定，从而可以有效的简化View和Model之间的状态同步。