How to achieve front-end and back-end separation in Nginx reverse generation database

With the rapid development of Internet technology, the idea of front-end and back-end separation is increasingly widely used by developers. The separation of front-end and back-end can separate and parallel the development of front-end and back-end, improve development efficiency, reduce development complexity, and improve system performance and scalability.

In an architecture where the front and back ends are separated, the front end requests data from the back end through the interface, and the back end processes the requested data and then returns it to the front end. In this process, Nginx can play a role in transmitting and forwarding data through reverse proxy technology. This article will introduce how to achieve front-end and back-end separation in Nginx reverse generation database.

1. Nginx reverse proxy database

In the architecture where the front and back ends are separated, the front end requests data from the back end through the interface and processes the returned data. If the database is directly exposed to the public network, there will be great security risks. Therefore, we need to use reverse proxy technology to proxy the data transmission process to ensure security.

In Nginx, the reverse proxy database can be implemented through the following configuration:

location /api/ { proxy_pass http://localhost:8080; }

The meaning of this configuration is that when the front end sends a request to the "/api/" path, Nginx will The request is forwarded to the local port 8080, and the data returned by the backend is forwarded back to the frontend. In this way, the security of the database can be guaranteed.

2. Nginx reverse generation load balancing

In actual applications, if the load on a single backend server is too large, the server's response time will slow down or even crash. Therefore, Nginx reverse generation load balancing technology needs to be used to balance the load of the backend server.

The load balancing configuration of Nginx is as follows:

upstream backend { server 127.0.0.1:8080; server 127.0.0.1:8081; } server { listen 80; server_name localhost; location /api/ { proxy_pass http://backend; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } }

This configuration means to forward the request to one of the back-end server clusters when one of the servers is busy or has a problem. , automatically switches to another server.

3. Nginx reverse generation cache

In an architecture where the front and back ends are separated, the front end needs to frequently send requests to the back end to obtain data. If each request requires re-reading from the database data, it will waste a lot of time and resources. At this time, you need to use Nginx's reverse generation caching function to cache frequently used data to improve the system's response speed and performance.

The cache configuration of Nginx is as follows:

proxy_cache_path /var/cache/nginx levels=1:2 keys_zone=my_cache:10m inactive=60m; server { listen 80; server_name localhost; location /api/ { proxy_pass http://backend; proxy_cache my_cache; proxy_cache_valid 200 60m; proxy_cache_valid 404 1m; proxy_cache_bypass $http_pragma; proxy_cache_revalidate on; proxy_cache_min_uses 2; proxy_cache_lock on; } }

The meaning of this configuration is to cache the data in the 10M cache area. If the cached data is not requested for a period of time, the cache will expire and be cleared. cache. At the same time, you can specify the cache time of different status codes through proxy_cache_valid, and you can also control cache updates through proxy_cache_bypass.

4. Nginx Reverse HTTPS

In an architecture where the front and back ends are separated, considering the security of data transmission, HTTP needs to be upgraded to HTTPS. In Nginx, you can implement reverse proxy HTTPS through the following configuration:

server { listen 443; server_name localhost; ssl on; ssl_certificate /etc/nginx/cert.pem; ssl_certificate_key /etc/nginx/key.pem; ssl_session_timeout 5m; location /api/ { proxy_pass http://backend; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } }

The meaning of this configuration is to listen to port 443, enable SSL configuration, and configure certificates and keys at the same time. At the same time, when proxying a request, relevant headers need to be set.

Summary

In the front-end and back-end separation architecture, Nginx plays a very important role. It realizes the secure transmission of data through reverse proxy technology, load balancing, caching and HTTPS functions. and improve the scalability of the system. Nginx is a very flexible and powerful reverse proxy server that can complete a variety of different tasks and application scenarios.

The above is the detailed content of How to achieve front-end and back-end separation in Nginx reverse generation database. For more information, please follow other related articles on the PHP Chinese website!