

#NGINX SSH PROXY UPDATE#
Nginx may also be configured to analyze the cached version and update it with changes accordingly. If the results of the requests already exist, then Nginx will quickly retrieve and serve the cached content. This allows Nginx to quickly retrieve and serve them to any other connections that are requesting the same content. If configured, it will also keep the results of the requests cached. Apache will handle the requests (forking/threading the requests) and then return the results to Nginx to serve to the client. If the results of the requests do not exist, then Nginx will provide the requests to Apache for processing.

Depending on Nginx’s configuration, when requests are made, it will first check to see if the processes have already been completed. Putting this all together, typically server administrators will combine the use of Apache and Nginx as a reverse proxy to decrease the server resources needed to load a site’s content. This results in a reduction of resources (like CPU, RAM, I/O) utilized and thus improves the performance of your site. This kind of proxy results in the ability to cache dynamic content without having to continuously rely on the server’s resources for each request to load the same content. When the results of the request are received by the proxy, it is then returned to the client. What is a Reverse Proxy?Ī Reverse Proxy is a type of configuration in which a proxy server off loads a request to another web server (or multiple servers) to execute processes. A common configuration that is implemented to improve the handling of a high load, is to setup Nginx as a reverse proxy. However, the benefits of Nginx can be experienced with simple web applications, like WordPress. Both connections receive the same results of content loaded.Īlthough Apache and Nginx performance can both be similar in comparing load handling for small sites, Nginx’s architecture, by design, is more efficient for heavier sites. For instance, if one connection requests the same content as another, rather than processing those requests individually, Nginx analyzes and delegates accordingly. Nginx alternatively scales these processes to help decrease the amount of CPU, RAM, and other server resources utilized, thus improving the load time. This means that Apache forks (or threads) each process that is needed to serve web content. In its default configuration, Apache is designed as a process-based architecture. On our servers, Apache is the default HTTP server that is configured for handling PHP processes to serve web content. In this manner, Nginx would be referred to as a reverse proxy. Because of its flexibility and lightweight design, it can also be installed along side Apache. Nginx is versatile, in that it can be installed to replace Apache as the HTTP server. Nginx is typically used to exploit higher performance from minimal resources, for example, on a VPS platform. This means the method by which Nginx handles processes (required for loading web content, for example) is driven by conditions and delegated to alternative server resources to bear the load accordingly.

In technical terms, it is an event-driven asynchronous server.

Nginx (pronounced “Engine-X”) is an open source, high-performance Hypertext Transfer Protocol (HTTP) server.
