NGINX

How it works

NGINX receives incoming network requests and follows configuration rules to handle them. It may return a static file directly or forward a request to an application running behind it. Caching can reduce repeated work, and load balancing distributes requests among services when an application uses several running instances.

What you can build

Set up website hosting, a shared entry point for web services, and traffic distribution for busy applications.

• Website delivery layer

  Serve images, stylesheets, and other website files while sending dynamic page requests to the application process responsible for generating the requested response.

• Shared application entry point

  Route requests for different services through one public entry point, with consistent handling for HTTPS, upstream destinations, and appropriate request size limits.

Things to consider

Configuration should match the application and hosting environment. Test redirects, caching, forwarded headers, and timeout behavior because incorrect rules can affect otherwise working pages.