상태 비저장 LLMs에 외부 메모리가 필요한 이유
각 API 호출이 처음부터 시작되는 이유, 단순한 컨텍스트 삽입이 토큰 한도를 폭발적으로 초과하게 되는 방식, 단순한 전략부터 복잡한 전략까지 메모리 전략의 설계 공간을 이해합니다.
상태 비저장 LLMs에 외부 메모리가 필요한 이유은(는) CoddyKit의 무료 AI Engineering Academy 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 AI Engineering Academy 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. AI Engineering Academy 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
LLMs Have No Memory by Default
Every API call to an LLM is completely independent. The model receives the messages you send in that single request and processes them — nothing more. When you make the next call, the model has no recollection of the previous conversation. It is as if you are speaking to someone with no short-term memory. This statelessness is by design: it makes models easier to scale and deploy, but it shifts the memory burden onto your application.
The Amnesia Problem in Practice
Without memory, a chatbot will fail basic multi-turn tasks. If a user says 'My name is Alice' in turn 1, then asks 'What is my name?' in turn 3, the model will say it does not know. Every turn appears to be a fresh conversation. Users find this deeply frustrating. The solution is for your application to maintain conversation history and include it in every API call.
# Naive stateless approach — model forgets everything
from openai import OpenAI
client = OpenAI()
def chat_stateless(user_message: str) -> str:
response = client.chat.completions.create(
model='gpt-4o-mini',
messages=[ # Only the new message — no history!
{'role': 'user', 'content': user_message}
]
)
return response.choices[0].message.content
chat_stateless('My name is Alice.') # Model: 'Hello Alice!'
chat_stateless('What is my name?') # Model: 'I do not know your name.'Naive Fix: Stuffing All History
The simplest memory approach is to append every turn to a growing list and send the entire list with each request. This works, but it has a critical flaw: the context window has a finite size. A 128K token window sounds large, but a long customer support chat with code snippets can exhaust it in minutes. Sending all history also means paying for the same tokens over and over.
messages = [] # grows with every turn
def chat_with_full_history(user_message: str) -> str:
messages.append({'role': 'user', 'content': user_message})
response = client.chat.completions.create(
model='gpt-4o-mini',
messages=messages # all history every time
)
reply = response.choices[0].message.content
messages.append({'role': 'assistant', 'content': reply})
return reply
# Works at first, but messages list grows unboundedly
# After 100 turns: could be 50,000+ tokens per requestThe Memory Design Space
There is a spectrum of memory strategies, each making different trade-offs between context fidelity (how much history is remembered) and token cost (how many tokens are used per request). The strategies from simplest to most sophisticated are: full buffer memory, sliding window memory, summary memory, entity memory, and vector-based episodic memory. The right choice depends on your conversation length and budget.
Token Cost of Conversation History
Each API call costs tokens based on the combined length of all messages — both the input (your messages array) and the output (the model's response). If you include the full history in every request, token cost grows quadratically with conversation length: turn N sends N previous messages. A 50-turn conversation with 200 tokens per turn sends 200+400+600+...+10,000 = over 250,000 input tokens total.
import tiktoken
def estimate_conversation_cost(
turns: int,
tokens_per_turn: int,
price_per_1k_input: float = 0.00015 # gpt-4o-mini
) -> float:
total_input_tokens = sum(
(i + 1) * tokens_per_turn # each turn sends all previous turns
for i in range(turns)
)
total_output_tokens = turns * tokens_per_turn
cost = (total_input_tokens / 1000) * price_per_1k_input
print(f'{turns} turns: {total_input_tokens:,} input tokens, ${cost:.4f}')
return cost
estimate_conversation_cost(50, 200)Where to Store Conversation History
Conversation history needs to be stored outside the Python process to survive server restarts and scale across multiple instances. Common storage backends include: Redis for fast in-memory access with TTL expiry (great for active sessions), PostgreSQL for durable long-term storage and analytics, and DynamoDB for serverless auto-scaling. LangChain provides connectors for all of these out of the box.
# Three storage options for conversation history
# 1. In-process dict (development only — lost on restart)
from langchain_core.chat_history import InMemoryChatMessageHistory
# 2. Redis (production — fast, TTL-based expiry)
from langchain_community.chat_message_histories import RedisChatMessageHistory
history = RedisChatMessageHistory(session_id='user-123', url='redis://localhost:6379')
# 3. PostgreSQL (production — durable, queryable)
from langchain_community.chat_message_histories import PostgresChatMessageHistory
history = PostgresChatMessageHistory(
session_id='user-123',
connection_string='postgresql://user:pass@localhost/db'
)Session IDs: Separating User Conversations
When your app serves multiple users, you need to maintain separate histories per conversation. A session_id (typically a UUID or a combination of user ID and conversation ID) identifies which history to load for each request. LangChain's RunnableWithMessageHistory accepts a get_session_history function that takes a session ID and returns the appropriate history object.
import uuid
from langchain_core.runnables.history import RunnableWithMessageHistory
from langchain_core.chat_history import InMemoryChatMessageHistory
store = {} # session_id -> history (use Redis in production)
def get_session_history(session_id: str) -> InMemoryChatMessageHistory:
if session_id not in store:
store[session_id] = InMemoryChatMessageHistory()
return store[session_id]
# Create a new session for each user conversation
def new_session() -> str:
return str(uuid.uuid4())
alice_session = new_session()
bob_session = new_session()
# Alice and Bob's histories are completely independentThe RunnableWithMessageHistory Wrapper
RunnableWithMessageHistory is LangChain's LCEL-native way to add memory to any chain. It wraps your chain, automatically loads history before each invocation, appends the new user message and AI response, and saves everything back to storage. You specify which input key contains the user message and which prompt variable should receive the history.
from langchain_openai import ChatOpenAI
from langchain_core.prompts import ChatPromptTemplate, MessagesPlaceholder
from langchain_core.runnables.history import RunnableWithMessageHistory
from langchain_core.output_parsers import StrOutputParser
prompt = ChatPromptTemplate.from_messages([
('system', 'You are a helpful assistant.'),
MessagesPlaceholder(variable_name='history'), # history injected here
('human', '{input}'),
])
chain = prompt | ChatOpenAI(model='gpt-4o-mini') | StrOutputParser()
chain_with_memory = RunnableWithMessageHistory(
chain,
get_session_history,
input_messages_key='input',
history_messages_key='history'
)Invoking a Memory-Enabled Chain
When invoking a chain wrapped with RunnableWithMessageHistory, you pass a config dict with configurable: {session_id: ...}. This tells the wrapper which history store to load. The chain handles everything else: loading history before the call, injecting it into the prompt, and saving the new turn after the response arrives.
session_id = 'user-alice-session-1'
# First message
response1 = chain_with_memory.invoke(
{'input': 'My name is Alice and I love Python.'},
config={'configurable': {'session_id': session_id}}
)
print(response1) # 'Hello Alice! Nice to meet you.'
# Second message — model now knows Alice's name and interest
response2 = chain_with_memory.invoke(
{'input': 'What is my name and what do I love?'},
config={'configurable': {'session_id': session_id}}
)
print(response2) # 'Your name is Alice and you love Python!'Memory Failure Modes to Avoid
Three common memory implementation mistakes: Forgetting session isolation — reusing one history object for all users leaks private data between conversations. Ignoring TTL — storing histories indefinitely fills your database; set expiry for inactive sessions. Over-trusting history — users can inject false memories ('I told you I am an admin') so validate claims against a source of truth rather than the conversation history alone.
# Mistake 1: Shared history for all users
global_history = InMemoryChatMessageHistory() # BAD!
# Fix: per-session history
store = {} # keyed by session_id
# Mistake 2: No TTL on Redis history
# BAD: history = RedisChatMessageHistory(session_id=sid, url=url)
# Good: set TTL to 24 hours
history = RedisChatMessageHistory(
session_id=session_id,
url='redis://localhost',
ttl=86400 # 24 hours in seconds
)Choosing Your Memory Strategy
Use full buffer memory only for short conversations where you know the total context will stay within limits. Use sliding window for general chatbots (keep last N turns). Use summary memory when conversations are open-ended and may be very long. Use vector memory when users need to recall specific facts from much earlier in a long conversation. We explore each of these in upcoming lessons.
Quick Check
Test your understanding of why stateless LLMs need external memory.
Lesson Recap
In this lesson you learned: LLMs are stateless by design — each API call sees only what you send in that request, naive full-history stuffing grows token costs quadratically and eventually hits context limits, and RunnableWithMessageHistory is LangChain's clean way to add external memory with any backend (Redis, PostgreSQL) keyed by session ID. Next up we explore specific memory strategies: buffer and window memory.
자주 묻는 질문
“상태 비저장 LLMs에 외부 메모리가 필요한 이유” 강의는 무료인가요?
네 — “상태 비저장 LLMs에 외부 메모리가 필요한 이유” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 AI Engineering Academy 강의 전체를 잠금 해제할 수 있습니다. AI Engineering Academy 강의에는 총 4개의 강의가 포함되어 있습니다.
“상태 비저장 LLMs에 외부 메모리가 필요한 이유”에서 뭘 배우나요?
각 API 호출이 처음부터 시작되는 이유, 단순한 컨텍스트 삽입이 토큰 한도를 폭발적으로 초과하게 되는 방식, 단순한 전략부터 복잡한 전략까지 메모리 전략의 설계 공간을 이해합니다. 브라우저에서 직접 실행하는 실습 코드로 AI Engineering Academy을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
AI Engineering Academy을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 AI Engineering Academy은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 1번째 강의입니다.
“상태 비저장 LLMs에 외부 메모리가 필요한 이유” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 AI Engineering Academy 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 AI Engineering Academy 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.
이 강의의 모든 강의
- 상태 비저장 LLMs에 외부 메모리가 필요한 이유
- 버퍼 및 윈도우 메모리
- 요약 메모리와 토큰 인식형 잘라내기
- Redis와 PostgreSQL에 채팅 기록 저장하기