It’s difficult to provide specific suggestions, it depends on your specific business. No matter which layer is reused, you need to have a deep understanding of that layer to see what can be shared. For forums, things like user login and registration, user level growth, user permissions and grouping, well, it sounds like backend business. , so the specific business depends on how well you can package it. Good reuse must be scalable. Try not to reuse things you don’t understand. Forced reuse will only bring costs to future use and maintenance. Understanding more about design patterns will be helpful in implementing reuse.
1. First of all, you need to consider whether the modular business can really be independent. 2. Secondly, the development of large teams should be plug-in. When the package is combined, choose the version of the corresponding module for packaging (if it reaches a certain deadline, If a certain plug-in has not been developed, just use its last released version) 3. In addition, it is necessary to consider the sinking of the basic business and being relied on by other plug-ins, such as: the information returned when logging in/registering
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It’s difficult to provide specific suggestions, it depends on your specific business. No matter which layer is reused, you need to have a deep understanding of that layer to see what can be shared. For forums, things like user login and registration, user level growth, user permissions and grouping, well, it sounds like backend business. , so the specific business depends on how well you can package it. Good reuse must be scalable. Try not to reuse things you don’t understand. Forced reuse will only bring costs to future use and maintenance. Understanding more about design patterns will be helpful in implementing reuse.
1. First of all, you need to consider whether the modular business can really be independent. 2. Secondly, the development of large teams should be plug-in. When the package is combined, choose the version of the corresponding module for packaging (if it reaches a certain deadline, If a certain plug-in has not been developed, just use its last released version)
3. In addition, it is necessary to consider the sinking of the basic business and being relied on by other plug-ins, such as: the information returned when logging in/registering