Shulou(Shulou.com)06/03 Report--

In this issue, the editor will bring you about the separation of the front and back end of the technology. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

1. Basic interaction technologies such as AJAX and JSON

2. HTTP protocol, the problem of cross-domain access caused by the same origin policy

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

Traditional separation method

When I mention the front end and the back end in my mind, basically the first difference that appears is that 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 just using the browser as the demarcation line to separate the two parts of the code. But the original purpose of front-end separation is to separate the responsibilities of front-end developers and solve the problem of development patterns. But it seems that their responsibilities were not clear before or even now, although the front end is to deal with the browser, but in the end the browser gets a temporary static page generated by the server through the template. So, in fact, the back end is involved because he has to deal with the template. Of course, there are generally two traditional modes of development collaboration:

One is to write a static page at the front end, and then let the back end set up the template. Static pages can be developed locally, regardless of the business logic, and you just need to implement View. The disadvantage is that the back-end set of templates is also required, and the back-end of the front-end code needs to be browsed to avoid errors.

Another collaboration model is that the front end writes the template directly. The problem is that the front end relies heavily on the back-end environment in the writing process, and the front end can hardly work if the back end is not finished.

Obviously there seems to be a lot of problems with both approaches, but at least that's the model that most companies have adopted so far. They distinguish the front and back end development from the physical layer, while diluting 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 front-end engineers. If you look at the requirements of front-end engineers when the company is hiring, there are additional design responsibilities in addition to the basic production skills of the page.

At this point, we thought we had separated the front and back ends, but on the awkward issue of templates, the front and rear engineers have definitely suffered a lot, because in the overall website architecture, this is not the separation of the front and back ends.

The above is what the editor shares with you about the separation of the front and back ends of the technology. If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.