Flask-Caching for response caching - Step-by-Step Execution

Concept Flow - Flask-Caching for response caching

Client sends request

↓

Check cache for response

Yes / No?↓

Return cached

↓

response

↓

Generate response

↓

Store response in cache

↓

Return response to client

This flow shows how Flask-Caching checks if a response is cached before processing a request, returns cached data if available, or generates and caches a new response.

Execution Sample

Flask

from flask import Flask
from flask_caching import Cache

app = Flask(__name__)
cache = Cache(app, config={'CACHE_TYPE': 'SimpleCache'})

@app.route('/')
@cache.cached(timeout=10)
def index():
    return 'Hello, cached world!'

This code sets up Flask-Caching to cache the '/' route response for 10 seconds.

Execution Table

Step	Action	Cache Check	Cache Hit?	Response Returned	Cache Update
1	Client requests '/' first time	Cache empty	No	Generate 'Hello, cached world!'	Store response in cache
2	Client requests '/' second time within 10s	Cache has response	Yes	Return cached 'Hello, cached world!'	No update
3	Client requests '/' after 10s timeout	Cache expired	No	Generate new 'Hello, cached world!'	Store new response in cache

💡 Caching stops when timeout expires or cache hit returns response immediately

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
cache['/']	None	'Hello, cached world!'	'Hello, cached world!'	'Hello, cached world!' (refreshed)

Key Moments - 2 Insights

Why does the first request generate the response but the second returns cached data?

At step 1 in the execution_table, the cache is empty so the response is generated and stored. At step 2, the cache has the response, so it returns cached data without regenerating.

What happens when the cache timeout expires?

At step 3, the cached response has expired, so the function runs again to generate a fresh response, which is then stored in the cache.

Visual Quiz - 3 Questions

Look at the execution_table, what is returned at step 2?

A Cached response from previous request

B A newly generated response

C An error message

D No response

💡 Hint

Check the 'Cache Hit?' and 'Response Returned' columns at step 2

At which step does the cache get updated with a new response?

A Step 1

B Step 2

C Step 3

D No step updates cache

💡 Hint

Look at the 'Cache Update' column for steps where response is stored

If the timeout was set to 0, what would happen to the cache behavior?

A Cache would update every request

B Responses would never be cached

C Responses would be cached forever

D Cache would cause errors

💡 Hint

Consider how timeout controls cache expiration in the variable_tracker and execution_table

Concept Snapshot

Flask-Caching stores route responses to speed up repeated requests.
Use @cache.cached(timeout=seconds) to cache a route.
On request, Flask checks cache first.
If cached, returns stored response immediately.
If not, runs function, caches result, then returns it.
Cache expires after timeout, forcing refresh.

Full Transcript

Flask-Caching helps speed up web responses by saving the output of routes. When a client asks for a page, Flask first looks in the cache. If the response is there and still valid, it sends it back right away. If not, Flask runs the route code to create the response, saves it in the cache, and then sends it. This saves time for repeated requests. The cache keeps responses only for a set time, called timeout. After timeout, the response is removed and the next request will generate a fresh response again.