TTL configuration in NestJS - Step-by-Step Execution

Concept Flow - TTL configuration

Start NestJS app

↓

Configure CacheModule

↓

Set TTL value in options

↓

Cache stores data with expiration

↓

Request data

↓

Check cache

This flow shows how NestJS CacheModule uses TTL (time-to-live) to expire cached data automatically after a set time.

Execution Sample

NestJS

import { CacheModule } from '@nestjs/common';

CacheModule.register({
  ttl: 5, // seconds
});

This code sets up NestJS cache with a TTL of 5 seconds, meaning cached data expires after 5 seconds.

Execution Table

Step	Action	TTL Setting	Cache State	Result
1	App starts and CacheModule registers	5 seconds	Empty	Cache ready with TTL=5s
2	Data requested first time	5 seconds	Empty	Cache miss, fetch data
3	Data cached with TTL=5s	5 seconds	Data stored with expiry timestamp	Data cached
4	Data requested within 5s	5 seconds	Data valid	Cache hit, return cached data
5	Wait 6 seconds (TTL expired)	5 seconds	Data expired	Cache miss, fetch fresh data
6	Data cached again with TTL=5s	5 seconds	New data stored with expiry	Data cached again

💡 Execution stops because TTL causes cached data to expire after 5 seconds, forcing fresh fetch.

Variable Tracker

Variable	Start	After Step 3	After Step 5	Final
cacheData	null	{value: 'data', expiresAt: t+5s}	null (expired)	{value: 'new data', expiresAt: t+5s}
ttl	5	5	5	5

Key Moments - 2 Insights

Why does the cache miss happen after 5 seconds even if data was cached before?

Because TTL is set to 5 seconds, cached data expires after that time (see execution_table step 5), so cache miss forces fresh data fetch.

What happens if TTL is not set in CacheModule?

Without TTL, cached data never expires automatically, so cache hit always returns old data unless manually cleared.

Visual Quiz - 3 Questions

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

A Cache empty

B Data valid and cached

C Data expired

D Cache disabled

💡 Hint

Refer to execution_table row with Step 4 showing cache state as 'Data valid'

At which step does the cached data expire due to TTL?

A Step 3

B Step 2

C Step 5

D Step 6

💡 Hint

Check execution_table row Step 5 where cache state is 'Data expired'

If TTL was set to 10 seconds instead of 5, how would step 5 change?

A Cache miss would happen later than step 5

B Cache miss would happen earlier than step 5

C Cache miss would happen exactly at step 5

D Cache miss would never happen

💡 Hint

TTL controls expiration time; longer TTL delays cache miss (see variable_tracker ttl value)

Concept Snapshot

NestJS CacheModule TTL configuration:
- Use CacheModule.register({ ttl: seconds }) to set expiration
- Cached data expires after TTL seconds automatically
- Cache hit returns data if not expired
- Cache miss fetches fresh data and caches it
- TTL helps keep cache fresh without manual clearing

Full Transcript

This visual execution shows how TTL (time-to-live) works in NestJS CacheModule. When the app starts, CacheModule is configured with a TTL value in seconds. When data is requested the first time, cache is empty, so data is fetched fresh and stored with an expiration timestamp based on TTL. Subsequent requests within TTL return cached data (cache hit). After TTL seconds pass, cached data expires, causing a cache miss on next request, which fetches fresh data again and caches it with a new expiration. Variables like cacheData track stored data and expiry time. Key moments include understanding why cache misses happen after TTL expires and what happens if TTL is not set. The quizzes test understanding of cache state at different steps and TTL effects. This helps beginners see how TTL keeps cache data fresh automatically.

Practice

1. What does TTL stand for in NestJS caching configuration?

easy

A. Timed Token Lock, a security feature for cache access

B. Time To Live, the duration cached data stays before removal

C. Temporary Transfer Lock, a pause on cache updates

D. Total Transaction Limit, the max number of cache writes

Solution

1. Step 1: Understand TTL meaning in caching

   TTL means how long cached data remains valid before it is removed automatically.

2. Step 2: Match TTL to the correct full form

   TTL stands for Time To Live, which fits the caching context perfectly.

3. Final Answer:

   Time To Live, the duration cached data stays before removal -> Option B

4. Quick Check:

   TTL = Time To Live [OK]

Hint: TTL means how long cache data lives before removal [OK]

Common Mistakes:

• Confusing TTL with security or transaction terms
• Thinking TTL is a cache size limit
• Assuming TTL is a manual cache clear command

2. Which is the correct way to set a global TTL of 10 seconds in NestJS cache module?

easy

A. CacheModule.register({ ttl: 10 })

B. CacheModule.register({ timeToLive: 10 })

C. CacheModule.register({ ttl: 10000 })

D. CacheModule.register({ expire: 10 })

Solution

1. Step 1: Identify TTL unit in NestJS cache config

   TTL is set in seconds, so 10 means 10 seconds.

2. Step 2: Check correct property name and value type

   The property is ttl, and the value is a number in seconds, so ttl: 10 is correct.

3. Final Answer:

   CacheModule.register({ ttl: 10 }) -> Option A

4. Quick Check:

   TTL in seconds uses 'ttl' property [OK]

Hint: TTL value is seconds, use 'ttl' property exactly [OK]

Common Mistakes:

• Using milliseconds instead of seconds
• Using wrong property names like timeToLive or expire
• Passing ttl as string instead of number

3. Given this NestJS cache config snippet:

CacheModule.register({ ttl: 5 })

What happens to cached data after 6 seconds?

medium

A. Cached data throws an error after 6 seconds

B. Cached data remains indefinitely until manually cleared

C. Cached data is refreshed automatically every 6 seconds

D. Cached data is automatically removed after 5 seconds

Solution

1. Step 1: Understand TTL effect on cached data

   TTL of 5 means cached data expires and is removed after 5 seconds.

2. Step 2: Check what happens after 6 seconds

   Since 6 seconds is more than 5, cached data is no longer valid and is removed.

3. Final Answer:

   Cached data is automatically removed after 5 seconds -> Option D

4. Quick Check:

   TTL 5 seconds means removal after 5 seconds [OK]

Hint: Data expires after TTL seconds, so 6 > 5 means removal [OK]

Common Mistakes:

• Thinking data stays forever without manual clear
• Assuming TTL refreshes cache automatically
• Believing cache throws errors on expiry

4. Identify the error in this NestJS cache TTL setup:

CacheModule.register({ ttl: '30' })

medium

A. TTL property name is incorrect, should be timeToLive

B. TTL cannot be set globally, only per item

C. TTL value should be a number, not a string

D. TTL value must be in milliseconds, not seconds

Solution

1. Step 1: Check TTL value type

   TTL expects a number representing seconds, but '30' is a string.

2. Step 2: Confirm correct property and units

   The property ttl is correct and uses seconds, so only the value type is wrong.

3. Final Answer:

   TTL value should be a number, not a string -> Option C

4. Quick Check:

   TTL must be numeric seconds, not string [OK]

Hint: TTL must be a number, not quoted string [OK]

Common Mistakes:

• Using string instead of number for TTL
• Changing property name incorrectly
• Confusing seconds with milliseconds

5. You want to cache user data with a TTL of 60 seconds, but override it to 120 seconds for admin users only. How do you configure TTL in NestJS?

hard

A. Set global TTL to 60, then use @CacheTTL(120) decorator on admin methods

B. Set global TTL to 120, then manually clear cache for non-admin users

C. Set TTL only in controller constructor based on user role

D. Use two separate CacheModules with different TTLs and switch dynamically

Solution

1. Step 1: Set global TTL for general users

   Configure CacheModule with ttl: 60 to cover normal users.

2. Step 2: Override TTL for admin users

   Use the @CacheTTL(120) decorator on admin-specific methods to extend TTL.

3. Final Answer:

   Set global TTL to 60, then use @CacheTTL(120) decorator on admin methods -> Option A

4. Quick Check:

   Global TTL + @CacheTTL override [OK]

Hint: Use global TTL plus @CacheTTL decorator for overrides [OK]

Common Mistakes:

• Trying to set TTL only in constructor without decorators
• Using multiple CacheModules unnecessarily
• Setting global TTL too high and clearing cache manually