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

This article mainly introduces "what are the advantages of web front-end separation". In daily operation, I believe many people have doubts about the benefits of web front-end separation. Xiaobian consulted all kinds of data and sorted out simple and easy-to-use methods of operation. I hope it will be helpful to answer the doubts about "what are the benefits of web front-end separation?" Next, please follow the editor to study!

The front and rear ends are not separated:

In the previous development method, the php code is written in HTML, and there is no pure PHP file and HTML file, which is the inseparability of the front and back end, that is, php and HTML have each other, while in the application mode in which the front end is not separated, what the front end sees is controlled by the backend, and the front end renders the page or is redirected, that is, the back end needs to control the display of the front end, and the coupling between the front end and the back end is very high. The requested data interaction is shown in the following figure:

For example:

Front-end engineers do not understand php code, and php engineers are not familiar with css and so on.

The development efficiency will be greatly reduced, such as writing static demo at the front end, translating the back end into VM templates, or directly based on the back-end environment, which is very troublesome to configure, install and use, and the front end still has to write VM and rely on back-end data, so the efficiency is still not high.

The performance of front-end capabilities is limited, such as performance optimization. If there is only limited space for performance optimization in the front-end, we often have to work with the back-end. However, due to the limitations of the back-end framework, it is difficult for us to optimize performance.

Finally, it is found that only when the front and rear ends are separated, can the above problems be solved thoroughly. So then there was the separation of the front and rear.

Front and rear separation:

Front end: responsible for View (view layer / display of HTML page) and Controller (logic layer / writing business logic) layer.

Backend: responsible for Model (data layer / data addition, deletion, modification and query) layer.

In the application mode in which the front end is separated from the front end, the back end only returns the data needed by the front end, no longer renders the HTML page, no longer controls the effect of the front end, what kind of effect the user sees and how the data requested from the back end is loaded into the front end, it is up to the front end to decide. The back end only needs to provide a set of logic to provide data, and the coupling between the front end and the back end is relatively low, in this mode. We usually turn each view of the back-end development into an interface, or API, and the front end adds, deletes, modifies and queries the data through the access interface.

The corresponding data interaction is shown below:

What are the benefits of front-end separation?

1. Build a lean team for quality products

Technical expertise, through the separation of front and rear, so that front-end engineers only need to focus on the front-end or back-end development work, cultivate the unique technical characteristics of front-end engineers, and then build a full-stack lean development team.

2. Improve work efficiency and make the division of labor clearer.

The front and back end separate workflow can make the front end focus on the front end, the back end care about the back end, both development at the same time, improve work efficiency, the increase of pages and routing changes do not have to bother the back end, the development is more flexible.

3. Local performance improvement

Through the configuration of the front-end routing, we can achieve the on-demand loading of the page, load all the resources of the website as soon as the home page is loaded out of order, and the server no longer needs to parse the front-end page, improving the page interaction and user experience.

4. Enhance the maintainability of the code

After the separation of the front and rear ends, the application code is no longer mixed with the front and rear ends, and the dependency relationship is invoked only at run time, and the hierarchy is clear, and the application code becomes clean and clear.

At this point, the study on "what are the benefits of web front-end separation" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.