I would like to ask, what is the concrete realization of the separation of front and rear ends?

  java, question

Is the front-end and rear-end separation different from the front-end port? If it is the same. So if Ali’s front and back ends are separated and there is excessive nodejs in the middle for intermediate caching and page rendering, but many of my current UIkit can provide enough api to enable users not to need another layer of page rendering, then I directly use nodejs for data caching, does that mean a large number of http Short link transfers (nodejs to java or php for data manipulation layer, etc.), I haven’t really understood what the separation between the front end and the back end is, and the front end like this is not basically downloaded directly. I mean, the whole front end can be saved by directly CTRL+s. although many have done enough JS uglify to make it difficult to modify even if it is taken away, I think the whole back end of the business logic can be done again. is that a loss? I am referring to SPA, because now many projects are basically done by SPA purely asynchronously. Ask for an answer!

The separation between front and back means that the person responsible for writing the presentation code and the person writing the business logic code can communicate as little as possible. As far as possible to determine as few interfaces as possible, two parts of the development can be independent of each other, do not need to finish one to write the other, can be independently tested.
This is how a large project is divided into two unrelated parts. The two parts are written separately. The less communication, the better. Ideally, there is no communication but it is impossible. Then the two parts can be put together and run. But also requires these two groups of people to master the less skills, the better, reduce the cost of manpower. If everyone knows the front end and the back end, it is not called separation of the front end and the back end, but called modularity. Of course, it is better to have Code reuse, easy maintenance and high code efficiency.
This does not seem to have a particularly good implementation plan.

What the landlord said is actually very good. All kinds of current methods have seen the shortcomings. The problem of decompiling and copying code has long existed.
http://www.yitaomin.cn/? p=187