The difference between MVC and MVP and MVVM

MVC,MVP,MVVM The difference between design architecture , I believe you all know these concepts .
First , Be clear , The purpose of architecture is to improve development efficiency , Reduce maintenance costs .
Using object-oriented design principles , Divide the responsibilities of each module reasonably , In order to let others better understand the architectural design idea , Then give each module a general term explanation , To better clarify data binding , Here is a brief explanation of several common architectures （ With Android For example ）.

• MVC：
  • The model layer （Model）, Responsible for processing data logic , Generally, it includes database 、 Local data 、 Internet access Bean Other components .
  • View layer （View）, Responsible for handling view display , Generally by XML The layout assumes this responsibility , Basic components and customization View As a supplementary element of the view layer .
  • Control layer （Control）, Responsible for handling business logic , Generally by Activity、Fragment Assume this responsibility .
• MVP：
  • The model layer （Model）, Responsible for processing data logic , Generally, it includes database 、 Local data 、 Internet access Bean Other components .
  • View layer （View）, Responsible for handling view display , Generally by XML The layout assumes this responsibility , Basic components and customization View As a supplementary element of the view layer ,Activity、Fragment Act as an adhesive between the view layer and the control layer .
  • Logic layer （Presenter）, Responsible for handling business logic , From the original MVC Extracted from the control layer Presenter Act as the control layer （Presenter）.
• MVVM：
  • The model layer （Model）, Responsible for processing data logic , Generally, it includes database 、 Local data 、 Internet access Bean、（ Here I extract the view data separately ViewData The concept also belongs to Model layer ） Other components .
  • View layer （View）, Responsible for handling view display , Generally by XML The layout assumes this responsibility , Basic components and customization View As a supplementary element of the view layer ,Activity、Fragment It is mainly responsible for the triggering of view layer binding events , Skilled words can also be directly in XML Binding trigger event in .
  • Logic layer （ViewModel）, Connect through data binding View and Model（ Here from ViewData Acting as a view model is bound to the view ） Realize the decoupling of view layer and model layer , Pass after the event is triggered ViewModel Process business logic , And modify the view data in a data-driven way , And achieve the function of indirectly modifying the view . Be careful ：ViewModel You must not hold a reference to the view layer , Also cannot hold Context References to ！ Or else MVP！

MVC,MVP,MVVM The difference between design architecture , I believe you all know these concepts .
First , Be clear , The purpose of architecture is to improve development efficiency , Reduce maintenance costs .
Using object-oriented design principles , Divide the responsibilities of each module reasonably , In order to let others better understand the architectural design idea , Then give each module a general term explanation , To better clarify data binding , Here is a brief explanation of several common architectures （ With Android For example ）.

• MVC：
  • The model layer （Model）, Responsible for processing data logic , Generally, it includes database 、 Local data 、 Internet access Bean Other components .
  • View layer （View）, Responsible for handling view display , Generally by XML The layout assumes this responsibility , Basic components and customization View As a supplementary element of the view layer .
  • Control layer （Control）, Responsible for handling business logic , Generally by Activity、Fragment Assume this responsibility .
• MVP：
  • The model layer （Model）, Responsible for processing data logic , Generally, it includes database 、 Local data 、 Internet access Bean Other components .
  • View layer （View）, Responsible for handling view display , Generally by XML The layout assumes this responsibility , Basic components and customization View As a supplementary element of the view layer ,Activity、Fragment Act as an adhesive between the view layer and the control layer .
  • ？？（Presenter）, Responsible for handling business logic , From the original MVC Extracted from the control layer Presenter Act as the control layer （Presenter）.
• MVVM：
  • The model layer （Model）, Responsible for processing data logic , Generally, it includes database 、 Local data 、 Internet access Bean、（ Here I extract the view data separately ViewData The concept also belongs to Model layer ） Other components .
  • View layer （View）, Responsible for handling view display , Generally by XML The layout assumes this responsibility , Basic components and customization View As a supplementary element of the view layer ,Activity、Fragment It is mainly responsible for the triggering of view layer binding events , Skilled words can also be directly in XML Binding trigger event in .
  • ？？（ViewModel）, Connect through data binding View and Model（ Here from ViewData Acting as a view model is bound to the view ） Realize the decoupling of view layer and model layer , Pass after the event is triggered ViewModel Process business logic , And modify the view data in a data-driven way , And achieve the function of indirectly modifying the view . Be careful ：ViewModel You must not hold a reference to the view layer , Also cannot hold Context References to ！ Or else MVP！