if everyone in the company knows both front and back, there's nothing to share. If you are the only one in the company, there is nothing to share. If there is a serious differentiation between the two levels of skills, it is necessary to divide them.

the so-called front-end separation means that the back-end only provides json data, and all the front-end data is requested through api, and then the request format follows the rules of restful. Of course, the back end needs to provide interface documentation.

more cutting-edge, graphql learn about

generally speaking, there are advantages and disadvantages, and the workload of front and rear separation naturally increases, but it will be more beneficial for employees who are more vertical in the skill tree. It is faster not to separate the pre-development, and the task of one person and one large module is directly taken away, but it is also painful to maintain, and it is not easy to expand