Separation of dynamic and static resources is to deploy website static resources (HTML, JavaScript, CSS, img, etc. files) separately from background applications to increase the speed of users accessing static code and reduce access to background applications.
One way to separate dynamic and static resources is to deploy static resources on nginx, deploy background projects to the application server, and request all static resource requests to the nginx server according to certain rules. Achieve the goal of separation of movement and stillness.
Benefits of nginx dynamic and static separation
api interface serviceization: After dynamic and static separation, the back-end application is more service-oriented, and it only needs to provide an api interface. Using it for multiple functional modules or even multiple platforms can effectively save back-end manpower and make function maintenance easier.
Parallel front-end and front-end development: The front-end and back-end only need to care about the interface protocol. Their respective developments do not interfere with each other. Parallel development and parallel self-testing can effectively increase development time and reduce joint debugging time to some extent.
Reduce the pressure on the back-end server and improve the access speed of static resources: the back-end no longer needs to render the template into html and return it to the client, and the static server can use more professional technology to improve the access speed of static resources.
For more Nginx related knowledge, please visit the Nginx usage tutorial column!
The above is the detailed content of The benefits of nginx dynamic and static separation. For more information, please follow other related articles on the PHP Chinese website!