Introduction to 2 deployment methods
The first one
Place an nginx server in front for http reverse Provide web services to nginx of the proxy and load balancing
behind n too server, and call the fast cgi service provided by php-fpm
this The first deployment method is the most common. Both web services and php services are deployed on the same server
The second one
One nginx server in front for web service
The back server only deploys php-fpm service for nginx server to call
Front One nginx server can also achieve load balancing when calling multiple php-fpm services later
as shown below:
Comparison
From a system design perspective
The first deployment is a conventional deployment method, which can be applied to large, medium and small-scale websites.
The second type is that different services are deployed on different servers, which is more detailed. But there are also several problems:
Front-end nginx acts as a web service. All static resource access, compression transfer and caching settings are centralized on this server. There will be a lot of pressure and it can easily become a bottleneck.
If the static resources are all stored in CDN and do not require HTTP compression transmission, this deployment method is quite reasonable;
Undertakes the above two , this deployment method can also be optimized. After the load balancing and reverse proxy layer in the front, there is an Nginx web server in the middle, and a PHP-FPM service is deployed behind it. From a performance perspective
Compared with the second deployment method, the first method requires one more inter-process interaction.
According to the first deployment, when an http request comes, first the nginx reverse proxy forwards it to the nginx web service (through the network), and the web service then communicates with php-fpm through the fastcgi protocol. Interaction (inter-process interaction);
According to the second deployment, when an http request comes, nginx acts as a web service and interacts directly with php-fpm through the network
In the first deployment, the http protocol is used to interact through the network, and in the second type, the fast-cgi protocol is used to interact through the network. How do these two protocols compare?
Fast cgi data packets will be slightly larger than http, and fast cgi protocol will carry more parameter information, transmission control information, etc. than http. The fast cgi protocol is more strictly formatted than the http protocol and is faster to parse. From an operation and maintenance perspective
The first is the most common deployment method, which is simple and unified. The services on all servers that provide web services are isomorphic, which is monotonous and extensive.
The second is to deploy nginx and php-fpm separately, and the distribution of different services on the server cluster is more detailed. If you count the pressure distribution in web services, you can make more precise use of hardware resources. Operation and maintenance costs are also higher.
From a development and testing perspective
Both deployment methods are not suitable for development or testing environments.
In the development and testing environment, nginx and php can be deployed on one server. Reverse proxy and load balancing are not required.
The above is the detailed content of What is the deployment method of Nginx and PHP. For more information, please follow other related articles on the PHP Chinese website!