[Python - 100 days since the novice to master] Day48 - separate back-end development before actual combat Django

Original link: https://github.com/jackfrued/Python-100-Days

[Python - 100 days since the novice to master]

Before and after the end of the separation development

In a traditional Web application development, most programmers will browser as the front and rear ends of the dividing line. All code section for users of the browser page display is called the front end, but will run on a server, providing the business logic and data preparation referred to as the front end of the rear end. The so-called separation of front and back end development, the agreement is good front and rear end engineer data exchange interfaces, parallel development and testing, to provide the back-end data only, not responsible for the data to render the page, front-end data acquisition via HTTP request and is responsible for rendering data onto the page, the job was handed browser JavaScript code to complete.

End of the separation development has many benefits before and after use, we briefly say that these benefits below:

  1. Enhance the development efficiency . After separation of the front and rear ends, you can decouple the front and rear side code, as long as the front and rear end communication applications require a good agreement, and interface parameters, you can begin to develop in parallel, without waiting for the other end of the development work. In this case, the front and rear end engineers can only focus on their own development work, helping to create a better team. In addition, the rear end of the front separating the development model, even if the requirements are changed, the same data format as long as the interface with the rear end of the developer does not need to modify the code, as long as the front end fluctuates.
  2. Enhanced code maintainability . Before and after the end of the separation, the application code is no longer front and rear end of the mixing, will only have to call dependencies at runtime, so maintaining your code will be a lot of work pleasant and relaxing, will no longer affect the situation as a whole. When your code becomes simple and clean, readable and maintainable code will enhance the quality.
  3. Service and support multi-terminal architecture . After separation of the front and rear ends, it may be provided with a data interface for different terminal services, but also help to build a multi-application terminal; In addition, since the interface between the rear end of the call can be provided through HTTP, help build service architecture ( including micro-services).

Guess you like

Origin blog.csdn.net/TeFuirnever/article/details/94475310