First, the understanding of the front-end framework

Referring to the framework is generally expected to be back-end use, especially the Java SSH Framework is very popular, these frameworks are based on the idea of MVC architecture. I understand that this is decoupled from the highest level, separating the data, the business, the view, both from understanding and from the actual workflow.

For back-end business composition: Database (db), service (sevice), Interface (Action), view.

Data tier-database

Control layer, specify the request to the response class, and then invoke the business service class in the response class, and the business service class obtains the data from the database for business processing to return to the response class when the response class is finished returning the data.

The front end of the view layer, issuing a request to the server, after the request succeeds, returns a data structure, usually key-value in the form of data.

Understand how to architect a front-end framework from a back-end workflow?

In fact, the front end is also composed of data, business, views, such as

Data-tier data model, front-end and background request interface data format.

Control layer 1. Instantiate the data model, 2. Process the business request, obtain the Entity Data model, and process the set-to-view.

A module (or Page) with the view layer, which is a data-driven display effect.

Although there are some differences, the essence is data, control, and view composition.

First, the understanding of the front-end framework