Micro-caching for dynamic content in Nginx - Step-by-Step Execution

Process Flow - Micro-caching for dynamic content

Client Request Arrives

↓

Check Cache for Response

↓

Cache Hit

↓

Serve Cached

↓

Store Response in Cache

↓

Send to Client

When a client requests dynamic content, nginx first checks if a cached version exists. If yes, it serves it quickly. If not, it generates the response, caches it briefly, then serves it.

Execution Sample

Nginx

proxy_cache_path /tmp/cache keys_zone=microcache:10m max_size=100m inactive=1m;

server {
  location /dynamic {
    proxy_cache microcache;
    proxy_cache_valid 200 1s;
    proxy_pass http://backend;
  }
}

This config sets up a micro-cache for dynamic content, caching successful responses for 1 second to speed up repeated requests.

Process Table

Step	Action	Cache State	Response Source	Notes
1	Client requests /dynamic	Empty	No cache	First request, cache empty
2	Check cache for /dynamic	Empty	Cache miss	No cached response found
3	Proxy request to backend	Empty	Backend	Request forwarded to backend server
4	Receive response 200 OK	Empty	Backend	Backend sends dynamic content
5	Store response in cache for 1s	Cache has /dynamic	Backend	Response cached briefly
6	Send response to client	Cache has /dynamic	Backend	Client receives fresh content
7	Client requests /dynamic again	Cache has /dynamic	Cache hit	Within 1 second, cache used
8	Serve cached response	Cache has /dynamic	Cache	Fast response from cache
9	Wait 1 second	Cache expires	Cache expired	Cache entry removed after 1s
10	Client requests /dynamic again	Cache empty	Cache miss	Cache expired, new backend request needed

💡 Cache entries expire after 1 second, so repeated requests within that time are served fast from cache.

Status Tracker

Variable	Start	After Step 5	After Step 8	After Step 9	After Step 10
cache_state	Empty	Has /dynamic	Has /dynamic	Expired (Empty)	Empty

Key Moments - 2 Insights

Why does nginx serve from cache on the second request but not the first?

Because at step 2 the cache is empty, so nginx forwards the request to backend (step 3). After receiving the response (step 4), it stores it in cache (step 5). On the second request (step 7), the cache has the response, so nginx serves it directly (step 8).

What happens when the cache expires after 1 second?

At step 9, the cached response expires and is removed. So at step 10, the cache is empty again, causing a cache miss and a new backend request.

Visual Quiz - 3 Questions

Look at the execution table, what is the cache state at step 6?

A Cache has /dynamic

B Cache empty

C Cache expired

D Cache miss

💡 Hint

Refer to the 'Cache State' column at step 6 in the execution table.

At which step does nginx serve the response from cache?

A Step 4

B Step 8

C Step 3

D Step 10

💡 Hint

Check the 'Response Source' column for 'Cache' in the execution table.

If the cache duration was increased to 10 seconds, what would change in the execution table?

A Cache would expire at step 9

B Cache would never expire

C Cache would expire after step 10

D Cache would expire before step 5

💡 Hint

Look at the 'Cache expires' note at step 9 and consider longer cache duration.

Concept Snapshot

Micro-caching in nginx:
- Use proxy_cache_path to define cache storage
- Enable proxy_cache in location block
- Set proxy_cache_valid for short duration (e.g., 1s)
- On request, nginx serves cached response if valid
- Otherwise, fetches from backend and caches it
- Speeds up dynamic content by reducing backend load

Full Transcript

Micro-caching for dynamic content in nginx works by storing responses for a very short time, like 1 second. When a client requests dynamic content, nginx first checks if it has a cached response. If yes, it serves it immediately, making the response faster. If not, it forwards the request to the backend server, gets the response, caches it briefly, and then sends it to the client. This process repeats, so repeated requests within the cache duration are served quickly from cache, reducing backend load. After the cache expires, nginx fetches fresh content again. This technique is useful for dynamic pages that change often but can tolerate very short caching to improve performance.

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