Уровень 0 · материалов: 6
В кластер входят документы, посвященные сравнению архитектур Nginx и Apache или техническому совмещению этих двух серверов в одной системе.
Общие признаки: использование Nginx в качестве обратного прокси перед Apache, оптимизация производительности веб-серверов, распределение нагрузки между статическим и динамическим контентом, архитектурные различия Nginx и Apache
Группа выше: Веб-серверы: Nginx и Apache
Смысл: The text provides a brief technical guide on how to configure Nginx as a front-end proxy for an Apache web server on Ubuntu. The primary goal is to optimize performance by letting Nginx handle static files and Apache handle dynamic requests.
A brief technical guide on setting up Nginx to handle static files while proxying dynamic requests to an Apache server on Ubuntu.
Смысл: The main idea is that using a default Apache configuration to serve static content is inefficient and can lead to server failure during traffic spikes, suggesting the use of Nginx as a reverse proxy for better performance.
A sudden surge of traffic from Habr crashed an old home server running Apache, demonstrating why Nginx is preferred for serving static content.
Смысл: The main idea is to maximize web server performance by leveraging the strengths of both Nginx (efficiency and concurrency) and Apache (compatibility and robustness) in a tiered architecture, supplemented by pre-compression of static assets.
A technical guide on using Nginx as a lightweight frontend proxy for a heavy Apache backend, combined with YUI Compressor and gzip_static for optimized content delivery.
Смысл: The main idea is to provide a technical walkthrough on how to use Nginx as a reverse proxy in front of Apache specifically when SSL is involved, highlighting common pitfalls like intermediate certificates, AJAX protocol mismatches, and application-specific URI issues.
A technical guide on setting up Nginx as an SSL-terminating reverse proxy for Apache, solving intermediate certificate and AJAX protocol issues.
Смысл: The text aims to educate developers and system administrators on the architectural and functional differences between Apache and Nginx to help them make an informed choice based on their specific performance and configuration needs.
A technical deep-dive comparing Apache's flexibility and module-rich environment with Nginx's high-performance, event-driven architecture for handling concurrent connections.
Смысл: The main idea is to explain the fundamental architectural difference between Apache (process-per-connection/prefork) and Nginx (event-driven/asynchronous) by demonstrating the underlying Linux system calls (socket, bind, listen, accept, fork, select, epoll).
The author uses progressive C coding examples to explain that Apache handles concurrency through multiple OS processes, while Nginx uses an event-driven loop with system calls like epoll to handle many connections in one process.