First of all, in terms of optimization, the static page transfers the pressure of server rendering templates to the client, which naturally reduces the pressure on service fees. In terms of expansion, data and pages are decoupled, and data interfaces can be reused. App, ria, webh5, frame-level themes, and a set of interfaces are all available. In the future, it can be expanded to dual servers, data services, and page services are separated. In terms of development, the front and rear responsibilities are separated, focusing on differences, and parallel development does not affect each other. The disadvantage is that optimizing the transfer increases the pressure on the browser (this pressure counts as a P). In terms of expansion, if the data interface does not follow the RESTful specification, some interface h5 cannot be called at all. Development increases personnel, increases learning costs, and pushes new reforms to offend people
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
First of all, in terms of optimization, the static page transfers the pressure of server rendering templates to the client, which naturally reduces the pressure on service fees. In terms of expansion, data and pages are decoupled, and data interfaces can be reused. App, ria, webh5, frame-level themes, and a set of interfaces are all available. In the future, it can be expanded to dual servers, data services, and page services are separated. In terms of development, the front and rear responsibilities are separated, focusing on differences, and parallel development does not affect each other.
The disadvantage is that optimizing the transfer increases the pressure on the browser (this pressure counts as a P). In terms of expansion, if the data interface does not follow the RESTful specification, some interface h5 cannot be called at all. Development increases personnel, increases learning costs, and pushes new reforms to offend people