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!

NGINX can improve website performance and reliability by: 1. Process static content as a web server; 2. forward requests as a reverse proxy server; 3. allocate requests as a load balancer; 4. Reduce backend pressure as a cache server. NGINX can significantly improve website performance through configuration optimizations such as enabling Gzip compression and adjusting connection pooling.

NGINXserveswebcontentandactsasareverseproxy,loadbalancer,andmore.1)ItefficientlyservesstaticcontentlikeHTMLandimages.2)Itfunctionsasareverseproxyandloadbalancer,distributingtrafficacrossservers.3)NGINXenhancesperformancethroughcaching.4)Itofferssecur

NGINXUnit simplifies application deployment with dynamic configuration and multilingual support. 1) Dynamic configuration can be modified without restarting the server. 2) Supports multiple programming languages, such as Python, PHP, and Java. 3) Adopt asynchronous non-blocking I/O model to improve high concurrency processing performance.

NGINX initially solved the C10K problem and has now developed into an all-rounder who handles load balancing, reverse proxying and API gateways. 1) It is well-known for event-driven and non-blocking architectures and is suitable for high concurrency. 2) NGINX can be used as an HTTP and reverse proxy server, supporting IMAP/POP3. 3) Its working principle is based on event-driven and asynchronous I/O models, improving performance. 4) Basic usage includes configuring virtual hosts and load balancing, and advanced usage involves complex load balancing and caching strategies. 5) Common errors include configuration syntax errors and permission issues, and debugging skills include using nginx-t command and stub_status module. 6) Performance optimization suggestions include adjusting worker parameters, using gzip compression and

Diagnosis and solutions for common errors of Nginx include: 1. View log files, 2. Adjust configuration files, 3. Optimize performance. By analyzing logs, adjusting timeout settings and optimizing cache and load balancing, errors such as 404, 502, 504 can be effectively resolved to improve website stability and performance.

NGINXUnitischosenfordeployingapplicationsduetoitsflexibility,easeofuse,andabilitytohandledynamicapplications.1)ItsupportsmultipleprogramminglanguageslikePython,PHP,Node.js,andJava.2)Itallowsdynamicreconfigurationwithoutdowntime.3)ItusesJSONforconfigu

NGINX can be used to serve files and manage traffic. 1) Configure NGINX service static files: define the listening port and file directory. 2) Implement load balancing and traffic management: Use upstream module and cache policies to optimize performance.

NGINX is suitable for handling high concurrency and static content, while Apache is suitable for dynamic content and complex URL rewrites. 1.NGINX adopts an event-driven model, suitable for high concurrency. 2. Apache uses process or thread model, which is suitable for dynamic content. 3. NGINX configuration is simple, Apache configuration is complex but more flexible.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

Atom editor mac version download
The most popular open source editor

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

SublimeText3 Mac version
God-level code editing software (SublimeText3)

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment
