التخزين المؤقت للوكيل والتخزين المخبئي

In web development, speed is crucial! Users expect fast loading times, and search engines reward performant sites.

Nginx, acting as a reverse proxy, can significantly enhance your application's speed and reliability.

Today, we'll explore two powerful Nginx features: buffering and caching.

Proxy buffering is when Nginx temporarily stores responses from your backend server before sending them to the client.

Think of it like a waiting room for data. Instead of sending data directly as it arrives, Nginx collects the full response (or parts of it) first.

This decouples the backend server from the client, improving efficiency.

Without buffering, Nginx acts as a simple relay. If the backend is slow, the client experiences that slowness directly.

With buffering, Nginx:

• Receives the full response from the backend.
• Stores it in its internal buffers (memory/disk).
• Sends the response to the client at the client's speed.

This protects your backend from slow client connections.

Buffering offers several key advantages:

• Frees Backend: Your backend server can finish sending its response quickly and serve other requests.
• Handles Slow Clients: Nginx can serve content to slow clients without holding up the backend.
• Improves Reliability: Prevents backend from being overwhelmed by network issues or slow connections.

Nginx uses specific directives to control buffering. Here are the main ones:

• proxy_buffering on;: Enables (or disables) buffering. It's usually on by default.
• proxy_buffers 4 8k;: Sets the number (4) and size (8KB) of buffers for a response.
• proxy_buffer_size 4k;: Sets the size of the first buffer, typically for response headers.

These are set within your location or http blocks.

Let's see a basic configuration to enable and configure buffering for a specific location:

This setup ensures Nginx buffers up to 32KB (4 buffers * 8KB each) of response data from the backend.

While buffering deals with how Nginx handles a single ongoing response, proxy caching stores copies of responses for future requests.

If multiple clients request the same resource, Nginx can serve it directly from its cache instead of asking the backend repeatedly.

This is a powerful way to reduce load on your backend servers.

When a request comes in:

1. Nginx checks its cache for a valid, stored response.
2. If found, it serves it immediately (cache hit).
3. If not, it forwards the request to the backend, receives the response, stores it in cache, and then serves it to the client (cache miss).

Benefits: Faster response times, reduced backend load, and improved scalability.

To set up caching, you need to define a cache zone and then apply it to your locations:

• proxy_cache_path /path/to/cache levels=1:2 keys_zone=my_cache:10m inactive=60m max_size=1g;: Defines the cache storage.
• proxy_cache my_cache;: Activates the named cache zone for a location.
• proxy_cache_valid 200 302 10m;: Sets how long responses with specific status codes are considered valid in cache.

Here's how to configure Nginx to cache static assets like images, CSS, or JavaScript files.

This example sets up a cache named 'static_cache' and uses it for requests to /assets/ paths, caching successful responses for 60 minutes.

Let's check your understanding of Nginx's performance features.

Great job! You've learned how Nginx can significantly improve application performance and backend resilience.

• Proxy buffering decouples backend and client, handling responses efficiently.
• Proxy caching stores responses to serve repeated requests faster and reduce backend load.

Mastering these features is key to building high-performance web applications with Nginx.