I am a bit ignorant, I have only heard of mvc model view controller Your way of understanding is not quite right The business interface is called in the web as you said, but you cannot just put the interface in the web. The business interface is a public thing. It may be called by other webs. It is abstract and convenient for decoupling, but it is still a business and cannot be included in the web. The same is true for dao
I feel like you don’t understand the interface very well. It is mainly about decoupling and reflection, and is not directly classified into the web
Maybe you think that the interface provides specifications, and changes in business requirements do not affect the web code - this is correct, but this is the function of the interface, not the architecture. I feel that you have made it very confusing
Most of them are written like this. However, the Web accepts user input, and service is the business interface. This kind has come out There is also DDD, you can take a look
1. The service layer is the business interface, and the web layer is here to accept user requests. 2. The service layer method not only plays a role in decoupling, but also can be reused by the web layer. 3. The controller layer, or RPC layer, is responsible for accepting web requests, mapping urls and methods, permission verification, paging control, etc. .
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
I am a bit ignorant, I have only heard of mvc
model
view
controller
Your way of understanding is not quite right
The business interface is called in the web as you said, but you cannot just put the interface in the web. The business interface is a public thing. It may be called by other webs. It is abstract and convenient for decoupling, but it is still a business and cannot be included in the web. The same is true for dao
I feel like you don’t understand the interface very well. It is mainly about decoupling and reflection, and is not directly classified into the web
Maybe you think that the interface provides specifications, and changes in business requirements do not affect the web code - this is correct, but this is the function of the interface, not the architecture. I feel that you have made it very confusing
Most of them are written like this.
However, the Web accepts user input, and service is the business interface.
This kind has come out
There is also DDD, you can take a look
1. The service layer is the business interface, and the web layer is here to accept user requests.
2. The service layer method not only plays a role in decoupling, but also can be reused by the web layer.
3. The controller layer, or RPC layer, is responsible for accepting web requests, mapping urls and methods, permission verification, paging control, etc. .
Hope it helps you~~~