Ask for advice!!
I love Segmentfault. So I refuse Baidu.
Reply content:
Ask for advice!!
I love Segmentfault. So I refuse Baidu.
Nutshell
The forward proxy is configured by the client, usually the client in an intranet, the server in the external network, the client through the proxy to access the server, which is usually transparent to the service side.
While the reverse proxy is configured by the server, the gateway that does the reverse proxy has an extranet address, and the business servers that actually have the ability to handle the request are not exposed directly to the external network. The URL resolves to the gateway's extranet address, and the gateway takes the user's request to access the Business Server and returns the results. This is exactly the opposite of the direction and logic of the forward proxy, which is transparent to the client.
Load balancing can be implemented by reverse proxy (the actual request is distributed across multiple business machines), and there are various uses such as the ability to monitor alarms, hide business servers, improve security, configure caching to reduce pressure on the business Server, and more.
The reverse proxy is not very clear,
When the amount of web traffic is large, it can cause the server to respond slowly or even deny service. This time how to solve, and put forward a kind of called load balancing strategy. Mainly scattered requests, a number of server sets and together, through a scheduler to spread the request on different machines.