Response caching strategies in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is response caching in Flask?

Response caching in Flask means saving the output of a web request so that future requests can be served faster without recalculating the response.

beginner

Name two common types of response caching strategies.

1. Client-side caching: The browser stores responses to reuse.
2. Server-side caching: The server stores responses to send quickly.

intermediate

How does Flask-Caching help with response caching?

Flask-Caching is an extension that makes it easy to store and retrieve cached responses on the server side using different backends like memory or Redis.

intermediate

What HTTP headers are important for client-side caching?

Headers like Cache-Control, Expires, and ETag tell browsers how long to keep a response and when to check for updates.

intermediate

Why should you be careful when caching dynamic content?

Because dynamic content changes often, caching it too long can show outdated information to users. You must set proper expiration or use cache invalidation.

Which Flask extension is commonly used for server-side response caching?

A Flask-Caching

B Flask-Login

C Flask-Mail

D Flask-WTF

Flask-Caching provides tools to cache responses on the server side.

What does the HTTP header Cache-Control: max-age=3600 mean?

A Cache only on the server

B Cache the response for 3600 seconds

C Do not cache the response

D Cache only on the client for 1 second

max-age=3600 tells browsers to keep the cached response for 3600 seconds (1 hour).

Which caching strategy stores responses in the user's browser?

A Database caching

B Server-side caching

C Client-side caching

D File system caching

Client-side caching means the browser saves responses to reuse later.

What is a risk of caching dynamic content too long?

A Showing outdated information

B Slower server response

C Increased bandwidth usage

D More database queries

Caching dynamic content too long can cause users to see old data.

Which HTTP header helps browsers check if cached content has changed?

A User-Agent

B Content-Type

C Authorization

D ETag

ETag is a unique identifier for a response version, helping browsers validate cache freshness.

Explain how you would implement server-side response caching in a Flask app.

Think about installing Flask-Caching and using decorators to cache views.

Describe the difference between client-side and server-side caching and when to use each.

Consider where the cached data lives and what benefits each provides.

Practice

1. What is the main purpose of response caching in a Flask application?

easy

A. To increase the size of the response data

B. To save server work and speed up response times

C. To make the server run slower intentionally

D. To disable user access temporarily

Solution

1. Step 1: Understand response caching

   Response caching stores the output of a request so the server doesn't have to recompute it every time.

2. Step 2: Identify the benefit

   This reduces server work and makes the app respond faster to repeated requests.

3. Final Answer:

   To save server work and speed up response times -> Option B

4. Quick Check:

   Response caching = save work & speed up [OK]

Hint: Caching speeds up responses by saving work [OK]

Common Mistakes:

• Thinking caching increases response size
• Believing caching slows down the server
• Confusing caching with access control

2. Which of the following is the correct way to cache a Flask route response for 60 seconds using Flask-Caching?

easy

A. @cache.cache(60)
def my_route():
return 'Hello'

B. @cache.cache(timeout=60)
def my_route():
return 'Hello'

C. @cache.cached(timeout=60)
def my_route():
return 'Hello'

D. @cached(60)
def my_route():
return 'Hello'

Solution

1. Step 1: Recall Flask-Caching decorator syntax

   The correct decorator is @cache.cached with a named argument timeout=60 to set cache duration.

2. Step 2: Check each option

   @cache.cached(timeout=60) def my_route(): return 'Hello' uses correct decorator and syntax. Options A and B use cache.cache which is invalid. @cached(60) def my_route(): return 'Hello' misses the cache. instance prefix.

3. Final Answer:

   @cache.cached(timeout=60) def my_route(): return 'Hello' -> Option C

4. Quick Check:

   Use @cache.cached(timeout=seconds) [OK]

Hint: Use @cache.cached with timeout= seconds [OK]

Common Mistakes:

• Using @cache.cache instead of @cache.cached
• Omitting the cache. prefix (@cached instead of @cache.cached)
• Using positional timeout argument

3. Given the code below, what will be printed on the second call to get_data() within 30 seconds?

@cache.cached(timeout=30)
def get_data():
    print('Fetching data...')
    return 'Data'

medium

A. Data

B. Fetching data...\nData

C. Fetching data...

D. Error: cache not found

Solution

1. Step 1: Understand caching effect on function calls

   The first call runs the function, prints 'Fetching data...', and caches the return 'Data'.

2. Step 2: Analyze second call within timeout

   Within 30 seconds, the cached result is returned directly, so the print statement does not run again.

3. Final Answer:

   Data -> Option A

4. Quick Check:

   Cached call skips print, returns cached 'Data' [OK]

Hint: Cached calls skip function body, return saved result [OK]

Common Mistakes:

• Expecting print output on every call
• Confusing cached return with function execution
• Assuming cache misses cause errors

4. Identify the error in this Flask caching code snippet:

@cache.cached(timeout=60)
def index():
    return render_template('index.html')

# Later in code
cache = Cache(app, config={'CACHE_TYPE': 'simple'})

medium

A. render_template cannot be cached

B. Timeout value must be a string, not integer

C. CACHE_TYPE 'simple' is invalid

D. Cache instance is created after using @cache.cached decorator

Solution

1. Step 1: Check order of cache setup and usage

   The decorator @cache.cached uses the cache object, but it is created after the function definition, so cache is undefined at decoration time.

2. Step 2: Validate other options

   Timeout as integer is valid. render_template output can be cached. 'simple' cache type is valid for development.

3. Final Answer:

   Cache instance is created after using @cache.cached decorator -> Option D

4. Quick Check:

   Define cache before using decorators [OK]

Hint: Create cache before decorating routes [OK]

Common Mistakes:

• Defining cache after using it in decorators
• Thinking timeout must be string
• Believing templates can't be cached

5. You want to cache different responses for a Flask route based on the logged-in user ID. Which caching strategy should you use to ensure each user gets their own cached response?

hard

A. Use @cache.cached(timeout=60, key_prefix=lambda: f'user_{current_user.id}')

B. Use @cache.cached(timeout=60, key_prefix=lambda: request.args)

C. Use @cache.cached(timeout=60, key_prefix=lambda: request.path)

D. Use @cache.cached(timeout=60) without key_prefix

Solution

1. Step 1: Understand caching by key prefix

   The cache stores responses by keys. To cache per user, the key must include the user ID.

2. Step 2: Evaluate options for key prefix

   Use @cache.cached(timeout=60, key_prefix=lambda: f'user_{current_user.id}') uses a lambda returning a string with the current user's ID, ensuring unique cache per user. Use @cache.cached(timeout=60, key_prefix=lambda: request.path) uses request path only, same for all users. Use @cache.cached(timeout=60, key_prefix=lambda: request.args) uses request arguments, which may not include user ID. Use @cache.cached(timeout=60) without key_prefix uses default key, same for all users.

3. Final Answer:

   Use @cache.cached(timeout=60, key_prefix=lambda: f'user_{current_user.id}') -> Option A

4. Quick Check:

   Cache key must include user ID for per-user caching [OK]

Hint: Include user ID in cache key prefix [OK]

Common Mistakes:

• Using only request path for cache key
• Ignoring user-specific cache needs
• Not using key_prefix for per-user caching