Micro-caching for dynamic content in Nginx - Commands & Configuration

Introduction

Sometimes dynamic websites take longer to respond because they generate content on the fly. Micro-caching helps by saving these dynamic pages for a very short time, so repeated requests get faster responses without waiting for full processing.

When your website has pages that change often but can be reused for a few seconds to reduce server load.

When you want to speed up API responses that are dynamic but tolerate a few seconds delay in showing new data.

When your server is slow to generate pages and you want to handle sudden bursts of traffic smoothly.

When you want to reduce database queries by caching dynamic content briefly.

When you want to improve user experience by serving faster responses without losing fresh content.

Config File - nginx.conf

nginx.conf

http {
    proxy_cache_path /tmp/nginx_cache levels=1:2 keys_zone=microcache:10m max_size=100m inactive=60m use_temp_path=off;

    server {
        listen 80;
        server_name example.com;

        location / {
            proxy_cache microcache;
            proxy_cache_valid 200 5s;
            proxy_cache_use_stale error timeout updating;
            proxy_pass http://backend_server;
            add_header X-Cache-Status $upstream_cache_status always;
        }
    }
}

proxy_cache_path defines where cache files are stored and how much memory is used for keys.

proxy_cache enables caching for this location using the defined cache zone.

proxy_cache_valid 200 5s caches successful responses for 5 seconds (micro-cache).

proxy_cache_use_stale serves stale content if backend is slow or down.

add_header X-Cache-Status adds a header to show if response was served from cache.

Commands

Check the nginx configuration file syntax to ensure there are no errors before reloading.

Terminal

sudo nginx -t

Expected Output

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok

nginx: configuration file /etc/nginx/nginx.conf test is successful

Reload nginx to apply the new configuration without stopping the server.

Terminal

sudo systemctl reload nginx

Expected Output

No output (command runs silently)

Send a request to the server and check headers to see if the response is cached (look for X-Cache-Status).

Terminal

curl -I http://example.com/

Expected Output

HTTP/1.1 200 OK

Server: nginx

X-Cache-Status: MISS

Date: Thu, 01 Jun 2023 12:00:00 GMT

Content-Type: text/html

Content-Length: 1234

Connection: keep-alive

Send the same request again shortly after to verify the response is served from cache (X-Cache-Status: HIT).

Terminal

curl -I http://example.com/

Expected Output

HTTP/1.1 200 OK

Server: nginx

X-Cache-Status: HIT

Date: Thu, 01 Jun 2023 12:00:02 GMT

Content-Type: text/html

Content-Length: 1234

Connection: keep-alive

Key Concept

If you remember nothing else from this pattern, remember: micro-caching stores dynamic content for a few seconds to speed up responses and reduce server load without losing freshness.

Common Mistakes

Setting micro-cache duration too long, like minutes or hours.

This causes users to see outdated dynamic content, defeating the purpose of micro-caching.

Use very short cache times like 5 seconds to keep content fresh but still gain speed.

Not testing nginx configuration before reload.

A syntax error can cause nginx to fail to reload, making the site unavailable.

Always run 'sudo nginx -t' to check config syntax before reloading.

Not adding headers to verify cache status.

Without headers, it's hard to confirm if micro-caching works or troubleshoot issues.

Add 'add_header X-Cache-Status $upstream_cache_status always;' to see cache hits and misses.

Summary

Define a cache zone with proxy_cache_path to store cached files.

Enable caching in the server location with proxy_cache and set a short cache time using proxy_cache_valid.

Reload nginx after configuration changes and verify caching works by checking response headers.

Practice

1. What is the main purpose of micro-caching dynamic content in nginx?

easy

A. To temporarily store dynamic pages to reduce server load and improve response time

B. To permanently save static files on the server

C. To disable caching for all dynamic content

D. To increase the size of the server's memory

Solution

1. Step 1: Understand micro-caching concept

   Micro-caching stores dynamic content briefly to reduce repeated processing and speed up responses.

2. Step 2: Identify the main benefit

   This reduces server load and improves response time during traffic spikes or frequent requests.

3. Final Answer:

   To temporarily store dynamic pages to reduce server load and improve response time -> Option A

4. Quick Check:

   Micro-caching = temporary dynamic content storage [OK]

Hint: Micro-caching means short-term caching of dynamic pages [OK]

Common Mistakes:

• Confusing micro-caching with permanent static caching
• Thinking micro-caching disables caching
• Assuming it increases server memory

2. Which nginx directive correctly sets micro-cache duration to 10 seconds?

easy

A. proxy_cache_duration 10s;

B. proxy_cache_valid 10s;

C. proxy_cache_valid 10m;

D. proxy_cache_time 10s;

Solution

1. Step 1: Recall correct directive for cache duration

   The directive to set cache validity time is proxy_cache_valid.

2. Step 2: Check correct time unit and syntax

   Using 10s sets cache duration to 10 seconds, which is valid syntax.

3. Final Answer:

   proxy_cache_valid 10s; -> Option B

4. Quick Check:

   Cache duration uses proxy_cache_valid [OK]

Hint: Use proxy_cache_valid with time unit for cache duration [OK]

Common Mistakes:

• Using wrong directive names like proxy_cache_duration
• Confusing seconds (s) with minutes (m)
• Omitting semicolon at end

3. Given this nginx config snippet:

proxy_cache_path /tmp/cache keys_zone=microcache:10m max_size=100m;
server {
  location /dynamic/ {
    proxy_cache microcache;
    proxy_cache_valid 5s;
    proxy_pass http://backend;
  }
}

What happens when a user requests /dynamic/page1 twice within 3 seconds?

medium

A. The second request is served from cache, speeding up response

B. The second request bypasses cache and fetches fresh content

C. Both requests cause backend to generate content

D. Cache is cleared after first request, so second fails

Solution

1. Step 1: Understand cache duration and behavior

   Cache duration is 5 seconds, so content is cached for 5 seconds after first request.

2. Step 2: Analyze requests timing

   Second request is within 3 seconds, so cache is still valid and serves cached content.

3. Final Answer:

   The second request is served from cache, speeding up response -> Option A

4. Quick Check:

   Cache valid 5s means repeated requests within 5s use cache [OK]

Hint: Requests within cache time get cached response [OK]

Common Mistakes:

• Assuming cache is bypassed before expiry
• Thinking cache clears after each request
• Confusing cache duration units

4. You configured micro-caching with:

proxy_cache_valid 10s;

But cache never stores responses. What is a likely cause?

medium

A. The server block lacks listen directive

B. The cache duration is too short to store anything

C. The proxy_pass URL is invalid

D. The proxy_cache_path directive is missing or incorrect

Solution

1. Step 1: Check required cache setup directives

   For caching to work, proxy_cache_path must define cache storage and zone.

2. Step 2: Identify missing or incorrect cache path

   If proxy_cache_path is missing or wrong, cache cannot store responses despite valid duration.

3. Final Answer:

   The proxy_cache_path directive is missing or incorrect -> Option D

4. Quick Check:

   proxy_cache_path must be set for caching to work [OK]

Hint: Always define proxy_cache_path to enable caching [OK]

Common Mistakes:

• Ignoring proxy_cache_path directive
• Blaming cache duration length
• Confusing proxy_pass errors with caching issues

5. You want to micro-cache dynamic API responses for 2 seconds but only cache successful responses (status 200). Which nginx config snippet achieves this?

hard

A. proxy_cache_valid 200 2s;
proxy_cache_valid 404 0s;

B. proxy_cache_valid 2s;
proxy_cache_use_stale error timeout;

C. proxy_cache_valid 200 2s;
proxy_cache_valid any 0s;

D. proxy_cache_valid 2s;
proxy_cache_min_uses 1;

Solution

1. Step 1: Understand proxy_cache_valid usage by status

   To cache only status 200 responses for 2 seconds, use proxy_cache_valid 200 2s;.

2. Step 2: Prevent caching other statuses

   Set proxy_cache_valid any 0s; to avoid caching other statuses like 404.

3. Final Answer:

   proxy_cache_valid 200 2s; proxy_cache_valid any 0s; -> Option C

4. Quick Check:

   Cache only 200 status with proxy_cache_valid [OK]

Hint: Use proxy_cache_valid with status code to control caching [OK]

Common Mistakes:

• Not specifying status code in proxy_cache_valid
• Using invalid directive names
• Caching error or 404 responses unintentionally