Web server and reverse proxy # Nginx web server deployment options Nginx can serve web content or proxy requests when configured. Capacity and performance depend on the service resources and workload. [Get started](https://panel.deplomo.com/signup)[View in marketplace](/marketplace) ## Nginx deployment considerations Review service availability, package limits, and configuration requirements before deployment. ### Load balancing across backends Nginx can distribute requests across configured backend servers using methods such as round robin or least connections. ### Event-driven reverse proxy Nginx uses an event-driven architecture. Connection capacity and memory use depend on configuration and workload. ### TLS termination and HTTP caching Nginx can terminate TLS and cache HTTP responses when configured. Review certificate, cache, and backend settings for your service. ### Modular configuration Nginx configuration can include redirects, headers, access rules, and proxy settings. DDoS protection depends on the broader network and service setup. ## Frequently asked questions about Nginx Answers to common questions about Apache, Nginx setup, and reverse proxy configuration: What is the Nginx web server, and how does it compare with Apache? Is Nginx deployment automated on Deplomo Cloud? Can Nginx serve static files and single-page applications? How do I connect a custom domain and TLS certificate to Nginx? ## Nginx architecture and deployment Nginx is a web server that can also act as a reverse proxy and load balancer. Its event-driven architecture supports concurrent connections; capacity and service availability depend on configuration and resources. ### What is Nginx, and how does it work? Nginx uses worker processes and an event-driven loop to handle network connections. Its resource use and connection capacity depend on the configured workers, modules, and workload. Nginx can serve static files, act as a reverse proxy or load balancer, cache HTTP responses, and terminate TLS when configured. Security and performance depend on the surrounding network and service setup. ### Nginx and Apache: configuration and deployment options When comparing [Apache web server](/marketplace/apps/apache) , consider their configuration models, modules, resource needs, and the workload. The table compares selected setup factors, not universal performance.
| Feature | Nginx container on Deplomo Cloud | Traditional Apache web server | Manual installation on an unmanaged VPS |
|---|---|---|---|
| Request handling model | Event-driven worker architecture | Configuration depends on the selected Apache model and modules | Resource use depends on server settings and workload |
| RAM memory consumption in high traffic | Resource use depends on configuration and workload | Resource use depends on configuration and workload | Capacity depends on operating-system settings and workload |
| The speed of rendering static files | Static-file performance depends on storage, cache headers, and network | Static-file performance depends on configuration and workload | Caching behavior depends on configuration |
| Deployment and setup | Availability and setup time depend on service status and configuration | Manual setup or control-panel options vary by provider | Manual setup depends on the operating system and administrator |
| Custom domains and TLS | Domain and certificate support depend on the deployment | Tools and licensing vary by platform | Certificate configuration and renewal depend on the environment |
| Load Balancing | Nginx supports modular configuration | Proxy features depend on modules and configuration | Upstream configuration depends on the deployment |