What technology is used to separate the front and back ends?

What technology is used to separate the front and back ends?

1. Basic interactive technologies such as AJAX and JSON;

2. HTTP protocol, cross-domain access issues caused by the same-origin policy;

3. Use NodeJs to build a middle-tier server and conduct front-end Mock testing.

Traditional separation method

When I mention front-end and back-end, they are basically the first ones that appear. The difference is: the back end deals with the database and the server, and the front end deals with the browser. There seems to be no problem, everyone thinks so. Of course, there is nothing wrong with this. We have always thought that we only use the browser as a boundary to separate these two parts of code. But the original intention of front-end and back-end separation is to separate the responsibilities of front-end and front-end developers and solve the problem of development model at the same time. But it seems that their responsibilities were not clear before or even now. Although the front end deals with the browser, the page the browser finally gets is just a temporary static page generated by the server through a template. So, the backend is actually involved because it has to deal with templates. Of course, there are generally two traditional development collaboration models:

One is to write a static page on the front end first, and then let the back end set the template after it is written. Static pages can be developed locally, and there is no need to consider business logic. You only need to implement View. The disadvantage is that you also need a back-end template, and these front-end codes need to be browsed by the back-end to avoid errors.

Another collaboration mode is for the front-end to write the template directly. The problem with this is that the front-end writing process relies heavily on the back-end environment. If the back-end is not finished, the front-end will hardly Law work.

Obviously there seem to be many problems with both methods, but at least this is the model adopted by most companies so far. They distinguish the development of front-end and front-end from the physical layer, while downplaying the logical color of the front-end. Since what the front-end does is to implement a static version of a page, most companies find some work for their front-end engineers. If you look at the current requirements for front-end engineers when companies are recruiting, in addition to basic page production skills, they also have additional design responsibilities.

At this point, we originally thought we had separated the front-end and back-end, but regarding the embarrassing issue of templates, the front-end and back-end engineers have definitely suffered a lot, because in terms of the overall website architecture, this is not Separation of front and back ends.

Recommended tutorials: "PHP" "JS Tutorial"

The above is the detailed content of What technology is used to separate the front and back ends?. For more information, please follow other related articles on the PHP Chinese website!