[Software Architecture Mode] The difference between MVVM mode and MVC mode

First, MVVM mode:

1.MVVM composition

MVVM consists of three parts: Model, View and ViewMode:

• Model: The model.The data model, which is used to operate on the data.
• View: The view. Represents UI components, which are used to convert model data into UI for display.
• ViewModel: View-Model. Used to synchronize Model and View.

Under the MWVM architecture, there is no direct connection between the View and the Model, but through the ViewModel. The interaction between the Model and the ViewModel is bidirectional, so the changes of the View data will be synchronized to the Model, and the ModelChanges in data will also be immediately reflected on the View.

ViewModel connects the View layer and the Mode layer through two-way data binding, and the synchronization between View and Model is completely automatic without human intervention, so developers only need to focus on business logic and do not need manual operationsDOM does not need to pay attention to the synchronization of data state, and complex data state maintenance is completely managed by MVVM.

2.MVVC pattern diagram

Second, the MVC pattern

1.MVC composition

MVC consists of three parts: Model, View, and Controller:

• Model: The model.The data model, which is used to operate on the data.
• View: The view. Represents UI components, which are used to convert model data into UI for display.
• Controller: The controller. For business logic processing, the Controller obtains data through the Model, and after processing, renders the data through the View.

Note: MVC mode is less efficient than MVVM mode, because MVC mode lacks ViewModel and will not automatically synchronize, developers need to constantly interfere in the development process.