MVVM and MVC

One 、 In the early mvc

Early pages usually consist of multiple PHP,jsp Document composition , This kind of code is difficult to maintain , So it extends mvc Development patterns and frameworks , The front-end presentation is in the form of a template , Typical frameworks such as spring etc. , This division structure has clear responsibilities , Code is easy to maintain , But here it is. mvc Limited to the back end , There's a certain separation between the front and rear ends , The front end has only completed the development view layer

shortcoming

1 The efficiency of front-end page development is not high

2 Unclear front and rear responsibilities

Two 、 front end mvc

With ajax The development of , The front end has been further developed , The front-end class libraries have also begun to develop, the most famous of which is jq, So the front end mvc With it

Similar to the back end , have view,controller,model,mvc The pattern is a single binding , namely model Bound to the view, When we use js Code update model when ,view It will automatically update

model Responsible for data storage , Synchronize with back-end data

controller Responsible for business logic , According to the user behavior model Data modification

view Responsible for view display , take model Visualize the data in

shortcoming ： Forced layering , A small function must go through such a process , Not flexible

3、 ... and 、mvvm Appearance

The three development modes can be said to represent web The process of field development , All to solve the problem of layering , solve model and view The coupling problem of