LLM Apps in Production (RAG + Vector DB + Caching) · Aula

Gerenciamento de Sessões e Persistência de Contexto

Aprenda a manter o estado das conversas e o contexto do usuário em várias interações, proporcionando uma experiência fluida com LLM.

Gerenciamento de Sessões e Persistência de Contexto é uma aula grátis de LLM Apps in Production (RAG + Vector DB + Caching) no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de LLM Apps in Production (RAG + Vector DB + Caching), e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de LLM Apps in Production (RAG + Vector DB + Caching) inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Why LLMs Need Memory

Imagine talking to someone who forgets everything you said a moment ago. That's often how Large Language Models (LLMs) work by default!

For a truly natural and helpful experience, LLM applications need to remember past interactions. This is where session management and context persistence come in.

LLMs: Stateless by Design

When you send a prompt to an LLM API, it processes that single request independently. It doesn't inherently 'remember' any previous prompts or responses.

Each API call is a fresh start.
This stateless nature is efficient for simple, one-off questions.
But it breaks down for conversations or personalized tasks.

Keeping the Conversation Flow

Context persistence is the technique of storing and retrieving relevant past information to include with new LLM requests.

This allows the LLM to understand the ongoing conversation, user preferences, or specific details provided earlier, making its responses much more coherent and useful.

Basic Strategy: Conversation History

The most common way to persist context for chat-based LLM applications is to maintain a conversation history.

Each user query and LLM response is added to a list.
Before sending a new user query, this entire history is included in the prompt.
This gives the LLM the full 'memory' of the interaction.

Simulating Chat History

Let's see a simple Python example where we build up a conversation history in a list. Notice how new messages are appended.

def simulate_chat():
  chat_history = []

  chat_history.append({"role": "user", "content": "Hi there!"})
  chat_history.append({"role": "assistant", "content": "Hello! How can I help?"})
  chat_history.append({"role": "user", "content": "What's the weather?"})

  print("--- Current Chat History ---")
  for msg in chat_history:
    print(f"{msg['role']}: {msg['content']}")

if __name__ == "__main__":
  simulate_chat()

Limitations of In-Memory History

While simple Python lists are great for demonstration, they have big limitations for real-world apps:

Ephemeral: Data is lost if the application restarts.
Single Session: Only works for one user's current interaction.
Scaling Issues: Not suitable for multiple concurrent users.

We need more robust solutions for persistence!

Storing Context Externally

To overcome in-memory limitations, context must be stored in an external, persistent system.

Common choices include:

Databases: SQL (PostgreSQL, MySQL) or NoSQL (MongoDB, Cassandra) for structured history.
Key-Value Stores: Redis or Memcached for fast access to session data.
Cloud Storage: Object storage like S3 for less frequent access.

Context in Action: LLM Call

When using external storage, the process looks like this:

User sends a new message.
Application retrieves the user's past conversation context from the external store.
The full context (history + new message) is sent to the LLM.
LLM generates a response.
The new response is added to the context and saved back to the external store.

Conceptual Code: Using Stored Context

This conceptual snippet shows how you'd load history and combine it with a new message before sending to an LLM. Assume load_history() and save_history() interact with an external store.

def send_to_llm_with_context(user_id, new_message):
  # Imagine these load/save from Redis/DB
  def load_history(uid): return [] # Placeholder
  def save_history(uid, hist): pass # Placeholder

  history = load_history(user_id)
  history.append({"role": "user", "content": new_message})

  # Construct the full prompt for the LLM
  llm_prompt = "".join([f"{msg['role']}: {msg['content']}\n" for msg in history])
  llm_prompt += "Assistant: "

  print(f"--- Sending to LLM ---\n{llm_prompt}")

  # Simulate LLM response
  llm_response = "I understand." 
  history.append({"role": "assistant", "content": llm_response})
  save_history(user_id, history)

if __name__ == "__main__":
  send_to_llm_with_context("user_123", "Tell me about context persistence.")

More Than Just Chat History

Context persistence isn't limited to just conversation history. It can also include:

User Profiles: Name, preferences, location.
Application State: Current task, active selections.
Document References: Which documents a user has interacted with.

This enriches the LLM's understanding and allows for truly personalized experiences.

Check Your Understanding

Understanding why LLMs need context is crucial for building robust applications.

Recap: Remembering the Past

In this lesson, we explored the critical role of session management and context persistence for LLM applications.

LLMs are stateless, requiring explicit context.
Conversation history is a primary form of context.
External storage (databases, Redis) is vital for robust persistence.
Context goes beyond chat, including user profiles and app state.

Mastering context persistence is key to creating intuitive and powerful LLM experiences!

Perguntas Frequentes

A aula “Gerenciamento de Sessões e Persistência de Contexto” é grátis?

Sim — o texto completo de “Gerenciamento de Sessões e Persistência de Contexto” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de LLM Apps in Production (RAG + Vector DB + Caching), atualize para CoddyKit PRO. O curso de LLM Apps in Production (RAG + Vector DB + Caching) inclui 4 aulas no total.

O que vou aprender em “Gerenciamento de Sessões e Persistência de Contexto”?

Aprenda a manter o estado das conversas e o contexto do usuário em várias interações, proporcionando uma experiência fluida com LLM. Você pratica LLM Apps in Production (RAG + Vector DB + Caching) com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar LLM Apps in Production (RAG + Vector DB + Caching)?

Nenhuma experiência prévia é necessária. LLM Apps in Production (RAG + Vector DB + Caching) no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “Gerenciamento de Sessões e Persistência de Contexto”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de LLM Apps in Production (RAG + Vector DB + Caching)?

Sim. Cada aula de LLM Apps in Production (RAG + Vector DB + Caching) inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

Cache Distribuído com Redis/Memcached
Gerenciamento de Sessões e Persistência de Contexto
Estratégias Avançadas de Invalidação de Cache
Cache semântico para respostas de LLM

← Voltar para LLM Apps in Production (RAG + Vector DB + Caching)