Comparison of the two deployment methods of PHP and Nginx (picture)

This article mainly introduces relevant information that explains in detail the comparison of the two deployment methods of Nginx and PHP. Friends who need it can refer to it.

Detailed explanation of the comparison between the two deployment methods of Nginx and PHP

2 deployment methodsIntroduction

The first one

• One nginx server in front for HTTP reverse proxy and load balancing

• Back Nginx of Nether Server provides web services and calls the fast cgi service provided by php-fpm

• This deployment method is the most common. Web services and PHP services are both on the same server. Deployment

##Second type

1. Prepare 1 nginx server for Web service

2. The back server only deploys the php-fpm service for the nginx server to call.

3. An nginx server is installed in the front. When calling multiple php-fpm services later, it can also be used. Achieve load balancing

From a system design perspective

##The front-end nginx acts as a Web service. Access to
• static

  resources, compression transmission, caching settings, etc. are also concentrated here. On a server. The pressure will be great and it can easily become a bottleneck.

If the static resources are stored in CDN and do not require HTTP compression transmission, this deployment method is relatively reasonable;
Following the above two points, this deployment method can also be optimized. For example, nginx load balancing and reverse proxy are placed in the front, nginx web service is in the middle, and php-fpm service is deployed behind. Perspective
Compared with the second deployment method, the first method requires one more inter-process interaction.

According to the first deployment method, When an http request comes, the nginx reverse proxy first forwards it to the nginx web service (through the network), and the web service interacts with php-fpm through the fastcgi protocol (inter-process interaction);
According to the second deployment, when an http request comes, nginx, which acts as a web service, interacts directly with php-fpm through the network
In the first deployment, the interaction through the network is HTTP protocol, the second type of interaction through the network is the fast-cgi protocol. How do these two protocols compare?

Fast cgi data packets will be slightly larger than HTTP, and the 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.

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.

If it is a LAMP environment deployment, the first type is more common.

If it is not LAMP, it is nginx interacting with other fastcgi services, such as C/C++ and Java fastcgi programs. In large-scale network applications, deployment similar to the second type is common. Separate deployment of different services simplifies the network structure of the system and makes maintenance easier.

The above is the detailed content of Comparison of the two deployment methods of PHP and Nginx (picture). For more information, please follow other related articles on the PHP Chinese website!