Caching strategies for cost reduction in LangChain - Step-by-Step Execution

Concept Flow - Caching strategies for cost reduction

Request comes in

↓

Check cache for data

↓

v

↓

Return cached

↓

Return data to user

This flow shows how a request first checks the cache to avoid extra API calls, reducing cost by reusing stored data.

Execution Sample

LangChain

cache = {}
def get_data(key):
    if key in cache:
        return cache[key]
    result = fetch_api(key)
    cache[key] = result
    return result

This code checks if data is cached; if not, it fetches from API, stores it, then returns it.

Execution Table

Step	Action	Key	Cache Before	Cache After	Returned Value
1	Check cache	user123	{}	{}	-
2	Cache miss, fetch API	user123	{}	{}	-
3	Store in cache	user123	{}	{'user123': 'data1'}	-
4	Return data	user123	{'user123': 'data1'}	{'user123': 'data1'}	data1
5	Check cache	user123	{'user123': 'data1'}	{'user123': 'data1'}	-
6	Cache hit, return cached	user123	{'user123': 'data1'}	{'user123': 'data1'}	data1

💡 After step 6, data is returned from cache, avoiding API call and saving cost.

Variable Tracker

Variable	Start	After Step 3	After Step 6
cache	{}	{'user123': 'data1'}	{'user123': 'data1'}
key	-	user123	user123
returned_value	-	-	data1

Key Moments - 2 Insights

Why does the code fetch from API only once for the same key?

Because after the first fetch, the result is stored in cache (see step 3), so next time the key is found in cache (step 5), avoiding API call.

What happens if the key is not in cache?

The code fetches data from the API (step 2), then stores it in cache (step 3) before returning it (step 4).

Visual Quiz - 3 Questions

Look at the execution table, what is the cache content after step 3?

A {}

B {'user123': 'data1'}

C {'user123': None}

D Cache is empty

💡 Hint

Check the 'Cache After' column in row for step 3.

At which step does the code avoid calling the API due to cached data?

A Step 6

B Step 2

C Step 4

D Step 1

💡 Hint

Look for 'Cache hit' and 'Return cached' in the Action column.

If the cache was empty, what would happen at step 1?

A Store data in cache

B Return cached data

C Fetch from API

D Exit without data

💡 Hint

Step 1 shows cache check; if empty, next step is API fetch.

Concept Snapshot

Caching Strategy for Cost Reduction:
- Check cache before API call
- If cache miss, fetch and store result
- Return cached data on hits
- Saves cost by reducing API calls
- Simple dict cache example shown

Full Transcript

This visual execution shows how caching works to reduce API costs. When a request comes in, the system first checks if the data is already stored in cache. If yes, it returns the cached data immediately, saving the cost of calling the API again. If not, it fetches the data from the API, stores it in cache, then returns it. The execution table traces each step, showing cache state changes and returned values. Key moments clarify why caching avoids repeated API calls and what happens on cache misses. The quiz tests understanding of cache content and flow. This strategy helps keep costs low by reusing data instead of fetching repeatedly.

Practice

1. What is the main benefit of using caching in Langchain to reduce costs?

easy

A. It automatically upgrades the Langchain version

B. It stores previous results to avoid repeated expensive calls

C. It deletes all data after each request to save memory

D. It increases the number of API calls to improve speed

Solution

1. Step 1: Understand caching purpose

   Caching saves results from previous operations to reuse them later.

2. Step 2: Connect caching to cost reduction

   By reusing stored results, it avoids repeated expensive API calls, lowering costs.

3. Final Answer:

   It stores previous results to avoid repeated expensive calls -> Option B

4. Quick Check:

   Caching = Avoid repeated calls [OK]

Hint: Caching saves results to skip repeated work [OK]

Common Mistakes:

• Thinking caching increases API calls
• Believing caching deletes data immediately
• Confusing caching with version upgrades

2. Which of the following is the correct way to use caching with Langchain's get_or_set method?

easy

A. cache.get_or_set(key, lambda: expensive_call())

B. cache.set_or_get(key, expensive_call())

C. cache.get_or_set(expensive_call(), key)

D. cache.get(key, expensive_call())

Solution

1. Step 1: Recall get_or_set syntax

   The method takes a key and a function to call if the key is missing.

2. Step 2: Match correct argument order

   Correct usage is cache.get_or_set(key, lambda: expensive_call()) to delay call until needed.

3. Final Answer:

   cache.get_or_set(key, lambda: expensive_call()) -> Option A

4. Quick Check:

   Correct method and argument order = B [OK]

Hint: Remember: key first, then function in get_or_set [OK]

Common Mistakes:

• Swapping key and function arguments
• Calling expensive function immediately instead of lazy
• Using wrong method names like set_or_get

3. Given this code snippet using Langchain caching:

cache = InMemoryCache()
result1 = cache.get_or_set('key1', lambda: 'data1')
result2 = cache.get_or_set('key1', lambda: 'data2')

What will be the value of result2?

medium

A. 'data2'

B. None

C. 'data1'

D. Raises an error

Solution

1. Step 1: Understand get_or_set behavior

   If the key exists, it returns cached value without calling the function.

2. Step 2: Apply to given code

   First call caches 'data1' under 'key1'. Second call finds 'key1' and returns 'data1', ignoring 'data2'.

3. Final Answer:

   'data1' -> Option C

4. Quick Check:

   Cache returns stored value, not new function result [OK]

Hint: get_or_set returns cached value if key exists [OK]

Common Mistakes:

• Assuming second lambda runs and returns 'data2'
• Expecting None if key exists
• Thinking it raises an error on duplicate keys

4. You wrote this code but it raises an error:

cache = RedisCache()
result = cache.get_or_set('key', expensive_call())

What is the likely cause of the error?

medium

A. You passed the result of expensive_call() instead of a function

B. RedisCache does not support get_or_set method

C. The key must be an integer, not a string

D. expensive_call() must be imported from langchain.cache

Solution

1. Step 1: Check get_or_set argument types

   get_or_set expects a key and a function to call if missing, not the function result.

2. Step 2: Identify error cause

   Passing expensive_call() calls it immediately, causing error or unwanted behavior.

3. Final Answer:

   You passed the result of expensive_call() instead of a function -> Option A

4. Quick Check:

   Pass function, not result, to get_or_set [OK]

Hint: Use lambda or function, not direct call, in get_or_set [OK]

Common Mistakes:

• Calling function instead of passing it
• Assuming RedisCache lacks get_or_set
• Using wrong key types

5. You want to reduce API costs by caching results in Langchain. Your app runs on multiple servers. Which caching strategy is best to share cached data across servers?

hard

A. Cache results only in local files on each server

B. Use an in-memory cache on each server separately

C. Disable caching to avoid stale data

D. Use a Redis cache shared by all servers

Solution

1. Step 1: Understand multi-server caching needs

   Multiple servers require a shared cache to avoid duplicate expensive calls.

2. Step 2: Evaluate cache types

   In-memory caches are local to each server; Redis is a shared external cache accessible by all servers.

3. Final Answer:

   Use a Redis cache shared by all servers -> Option D

4. Quick Check:

   Shared cache for multi-server = Redis [OK]

Hint: Use shared Redis cache for multi-server apps [OK]

Common Mistakes:

• Using local in-memory cache for multi-server apps
• Disabling caching unnecessarily
• Relying on local files which are not shared