In the last year, I used the yog2 framework in some practical aspects of the service, and some thoughts should be sent. Now, the architecture of the web is based on the node.js yog2 framework.
The YOG2 framework provides automatic routing and multi-level routing system based on express routing. The goal is to make the UI layer more efficient, more formal, and more flexible.
YOG2’s route is divided into two classes. One is the root route, whose role is very similar to the traditional Express route, which is the consistent entry of all requests, so we have the maximum degree of freedom in the root route and can do any forwarding. The other type is app routing, which can only receive requests from root routes to various apps. How can the requests be distributed in the app and can be completely controlled by the app?
Real-time compilation of fis3 is extremely efficient
Routing automatic matching
Project split, the concept of modularity is very strong.
Node. Js express extension
Yog2 provides the logging module
Yog2 provides ral for centralized processing of service requests.
The layout of the project organization is chaotic.
The default template engine swig is hard to use.
- Quickly generate a project, node server project shelf.