nginx is an http web server that can store static files on the server (html, css, pictures) are returned to the browser client through the HTTP protocol.
Example: We deploy a static resource index.html on the server
Upload index.html to linux /opt/www/test
Modify nginx.conf and add a location to intercept requests for /test. The /opt/www path corresponding to root represents the root path, which is the /slash in front of /test
location /test { root /opt/www; index index.html; }
Start nginx or reload nginx
Let’s visit: http://192.168.253.130/test/
Load balancing can be divided into hardware load balancing and software load balancing
Hardware load balancing, such as F5, Sangfor, Array, etc., has the advantage of being supported by the manufacturer's professional team. Stable performance; the disadvantage is that it is expensive
Software load balancing, such as Nginx, LVS, HAProxy, etc. The advantage is that it is free and open source and low cost
Polling method: allocate requests in turn to On the backend server, it treats each backend server equally, regardless of the actual number of connections to the server and the current system load.
http { upstream test{ ##后端实际服务器 nginx在轮询访问以下几台服务器 server 10.100.30.1:8080; server 10.100.30.2:8080; server 10.100.30.3:8080; server 10.100.30.4:8080; } server { ##前端拦截入口 listen 80; server_name www.test.com; location / { proxy_pass http://test; } } }
Weighted polling method: Different back-end servers may have different machine configurations and current system loads, so their pressure resistance is also different.
Assign a higher weight to a machine with high configuration and low load to allow it to handle more requests; and assign a lower weight to a machine with low configuration and high load to reduce its system load. Weighted polling handles this problem very well and distributes requests to the backend in order and according to weight.
http { upstream test{ ##后端实际服务器 nginx在轮询访问以下几台服务器 server 10.100.30.1:8080 weight=1; server 10.100.30.2:8080 weight=3; server 10.100.30.3:8080 weight=1; server 10.100.30.4:8080 weight=1; } server { ##前端拦截入口 listen 80; server_name www.test.com; location / { proxy_pass http://test; } } }
Source address hashing method: According to the IP address of the client, a value is calculated through the hash function, and the value is used to perform a modulo operation on the size of the server list. The result obtained is the client request. Serial number to access the server.
Using the source address hash method for load balancing, a client with the same IP address will be mapped to the same backend server for access every time when the backend server list remains unchanged.
upstream test{ ip_hash; server 10.100.30.1:8080 weight=1; server 10.100.30.2:8080 weight=3; server 10.100.30.3:8080 weight=1; server 10.100.30.4:8080 weight=1; }
Minimum number of connections method: Since the configuration of the back-end server is different, the processing of requests may be faster or slower. The minimum number of connections method dynamically selects the current backlog based on the current connection status of the back-end server. The server with the least number of connections will handle the current request, improve the utilization efficiency of the back-end service as much as possible, and reasonably distribute the responsibility to each server.
upstream test{ least_conn; server 10.100.30.1:8080; server 10.100.30.2:8080; server 10.100.30.3:8080; server 10.100.30.4:8080; }
down: Indicates stopping a certain service
upstream test{ server 10.100.30.1:8080 down; server 10.100.30.2:8080; server 10.100.30.3:8080; server 10.100.30.4:8080; }
backup: Specifies the backup server. Under normal circumstances, as long as other servers can access it normally, the backup server will not be accessed, only other servers. The standby server will only be used when all are down, so this method is generally used to implement hot deployment. The code is updated to the standby server first, and then the normal server is stopped. After the normal server deployment is completed, the standby server is waiting again. status, the entire deployment process enables users to experience no downtime.
upstream test{ server 10.100.30.1:8080 backup; server 10.100.30.2:8080 backup; server 10.100.30.3:8080; server 10.100.30.4:8080; }
Static proxy
##Separation of dynamic and static
Virtual host
server { listen 80; server_name example.com; location / { root /usr/share/nginx/html; index index.html index.htm; } location /images/ { alias /var/www/images/; } location /downloads/ { alias /var/www/downloads/; } }
upstream backend { server backend1.example.com:8080 weight=3; server backend2.example.com:8080; } server { listen 80; server_name example.com; location / { proxy_pass http://backend; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; } }
上述配置中，Nginx会将访问根目录（/）的请求转发给后端的Web服务器（backend1.example.com和backend2.example.com），其中backend1.example.com的权重为3，backend2.example.com的权重为1，表示backend1.example.com的处理能力更强。
在转发请求时，Nginx还会设置HTTP头信息中的Host和X-Real-IP字段，从而隐藏Web服务器的真实IP。
在使用Nginx作为负载均衡器时，Nginx会将请求均衡地分发到多个Web服务器上，从而实现高并发、高可用的服务。这种场景通常用于Web应用程序的集群部署、分布式系统的部署等。下面是一个示例Nginx配置：
upstream backend { server backend1.example.com:8080; server backend2.example.com:8080; server backend3.example.com:8080; } server { listen 80; server_name example.com; location / { proxy_pass http://backend; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; } }
上述配置中，Nginx会将请求均衡地分发到三个Web服务器（backend1.example.com、backend2.example.com和backend3.example.com）上，从而实现负载均衡。
在转发请求时，Nginx还会设置HTTP头信息中的Host和X-Real-IP字段，从而隐藏Web服务器的真实IP。
在使用Nginx作为缓存服务器时，Nginx会缓存Web服务器返回的响应，从而减少对Web服务器的请求。这种场景通常用于提高Web应用程序的性能、降低Web服务器的负载等。下面是一个示例Nginx配置：
proxy_cache_path /var/cache/nginx levels=1:2 keys_zone=my_cache:10m inactive=60m; server { listen 80; server_name example.com; location / { proxy_cache my_cache; proxy_pass http://backend; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; } }
上述配置中，Nginx会将Web服务器返回的响应缓存到/var/cache/nginx/my_cache目录下，并设置缓存有效期为60分钟。在缓存命中时，Nginx会直接返回缓存的响应，从而减少对Web服务器的请求。
总之，Nginx具有很强的可扩展性和灵活性，可以根据不同的需求配置不同的使用场景。以上仅是一些示例，实际应用中还有很多其他的使用场景。
在使用Nginx作为反向代理服务器时，Nginx会将客户端请求转发到后端的Web服务器上，并将后端服务器返回的响应转发给客户端。这种场景通常用于隐藏后端服务器的真实IP、提高Web应用程序的可用性等。下面是一个示例Nginx配置：
server { listen 80; server_name example.com; location / { proxy_pass http://backend; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; } }
上述配置中，Nginx会将客户端请求转发到http://backend上，并设置HTTP头信息中的Host和X-Real-IP字段，从而隐藏后端服务器的真实IP。
在使用Nginx作为WebSocket服务器时，Nginx会将客户端请求转发到后端的WebSocket服务器上，并实现WebSocket协议的连接管理。这种场景通常用于实时通信、游戏等应用程序。
下面是一个示例Nginx配置：
map $http_upgrade $connection_upgrade { default upgrade; '' close; } server { listen 80; server_name example.com; location / { proxy_pass http://backend; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; } }
上述配置中，Nginx会将WebSocket请求转发到http://backend上，并设置HTTP头信息中的Upgrade、Connection、Host和X-Real-IP字段，从而实现WebSocket协议的连接管理。
总之，Nginx具有很多的使用场景，可以根据不同的需求配置不同的服务器功能。以上仅是一些示例，实际应用中还有很多其他的使用场景。
The above is the detailed content of What are the main application scenarios in Nginx?. For more information, please follow other related articles on the PHP Chinese website!
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
