Tratamento de Erros e Padrões de Resiliência
Projete tratamento robusto de erros, mecanismos de repetição e disjuntores para tornar suas aplicações de LLM mais tolerantes a falhas.
Tratamento de Erros e Padrões de Resiliência é uma aula grátis de LLM Apps in Production (RAG + Vector DB + Caching) no CoddyKit. Esta é a aula 3 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.
Build Robust LLM Apps
LLM applications, especially those interacting with external APIs, need to be tough!
Resilience is about designing systems that can recover from failures gracefully, without crashing or providing a bad user experience.
In this lesson, we'll learn patterns to make your LLM apps more fault-tolerant.
Typical Failures
What kind of errors can an LLM application face?
- API Rate Limits: Too many requests at once.
- Network Issues: Temporary connection drops.
- LLM Service Unavailability: The LLM provider is down.
- Bad LLM Responses: Model returns invalid JSON or hallucinates.
- Dependency Failures: Vector DB or other services fail.
Standard Try-Catch
The first line of defense is standard error handling using try-catch blocks. This prevents your entire application from crashing when an expected error occurs.
It allows you to log the error, inform the user, or attempt a fallback.
public class Main {
public static void main(String[] args) {
try {
// Simulate an LLM API call that might fail
callLlmApi();
System.out.println("API call successful.");
} catch (Exception e) {
System.out.println("Error: " + e.getMessage());
// Log the error, notify user, etc.
}
}
public static void callLlmApi() throws Exception {
// In a real app, this would make an actual API call
if (Math.random() < 0.5) { // 50% chance of failure
throw new RuntimeException("LLM service unavailable.");
}
}
}Why Just Catching Isn't Enough
Some errors are transient, meaning they're temporary and might resolve if you just try again. Think of a brief network glitch or a momentary rate limit.
A simple try-catch just fails immediately. For transient errors, a retry mechanism can significantly improve reliability without user intervention.
Simple Retry Logic
We can implement a basic retry loop. If an error occurs, we wait a bit and try again, up to a maximum number of attempts.
public class Main {
public static void main(String[] args) {
int maxRetries = 3;
int currentRetry = 0;
boolean success = false;
while (currentRetry < maxRetries && !success) {
try {
System.out.println("Attempt " + (currentRetry + 1));
callLlmApi();
System.out.println("API call successful.");
success = true;
} catch (Exception e) {
System.out.println("Error: " + e.getMessage());
currentRetry++;
if (currentRetry < maxRetries) {
System.out.println("Retrying in 1 second...");
try { Thread.sleep(1000); } catch (InterruptedException ie) {}
}
}
}
if (!success) {
System.out.println("All retries failed.");
}
}
public static void callLlmApi() throws Exception {
// Simulate an LLM API call with 70% chance of failure
if (Math.random() < 0.7) {
throw new RuntimeException("Transient network error.");
}
}
}Smart Retries: Exponential Backoff
Constant retry delays can overwhelm a struggling service. Exponential backoff is a strategy where the delay between retries increases exponentially.
This gives the remote service more time to recover and prevents your app from hammering it with requests.
- Initial delay: 1s
- Second delay: 2s
- Third delay: 4s
- And so on...
Circuit Breaker Pattern
What if a service is truly down, not just experiencing transient errors? Retrying repeatedly only wastes resources and delays failure detection.
The Circuit Breaker pattern prevents an application from repeatedly trying to invoke a service that is likely to fail, saving resources and allowing the service time to recover.
Circuit Breaker States
A circuit breaker has three main states:
- Closed: Operations proceed normally. If errors exceed a threshold, it trips to Open.
- Open: All requests fail immediately without trying the service. After a timeout, it transitions to Half-Open.
- Half-Open: A limited number of requests are allowed to pass through to test if the service has recovered. If successful, it goes back to Closed; otherwise, back to Open.
Preventing Hung Requests with Timeouts
LLM API calls can sometimes hang indefinitely, waiting for a response that never comes. This can exhaust resources and degrade user experience.
Always configure timeouts for your API calls. This sets a maximum duration your application will wait for a response before giving up and throwing an error.
import java.util.concurrent.TimeUnit;
public class Main {
public static void main(String[] args) {
long startTime = System.nanoTime();
long timeoutMillis = 2000; // 2 seconds timeout
try {
System.out.println("Calling LLM API with a timeout...");
callLlmApiWithTimeout(timeoutMillis);
System.out.println("API call completed successfully.");
} catch (Exception e) {
System.out.println("API call failed: " + e.getMessage());
}
long endTime = System.nanoTime();
long duration = TimeUnit.NANOSECONDS.toMillis(endTime - startTime);
System.out.println("Total duration: " + duration + "ms");
}
public static void callLlmApiWithTimeout(long timeoutMillis) throws Exception {
// Simulate a long-running/hung API call
long processingTime = 2500; // 2.5 seconds
if (processingTime > timeoutMillis) {
throw new RuntimeException("Operation timed out after " + timeoutMillis + "ms");
}
try {
Thread.sleep(processingTime);
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
throw new RuntimeException("API call interrupted.", e);
}
}
}Resilience Check
When should you use a Circuit Breaker pattern instead of just a Retry mechanism?
Recap: Building Resilient LLM Apps
We've covered key patterns for making your LLM applications fault-tolerant:
- Basic Error Handling: Using
try-catchfor immediate failure management. - Retry Mechanisms: For handling transient errors, often with exponential backoff.
- Circuit Breakers: To prevent overwhelming consistently failing services.
- Timeouts: Essential for preventing hung API calls and resource exhaustion.
These patterns are crucial for robust production LLM systems!
Perguntas Frequentes
A aula “Tratamento de Erros e Padrões de Resiliência” é grátis?
Sim — o texto completo de “Tratamento de Erros e Padrões de Resiliência” é 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 “Tratamento de Erros e Padrões de Resiliência”?
Projete tratamento robusto de erros, mecanismos de repetição e disjuntores para tornar suas aplicações de LLM mais tolerantes a falhas. 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 3 de 4.
Quanto tempo leva a aula “Tratamento de Erros e Padrões de Resiliência”?
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
- Protegendo Chaves de Interfaces de LLM e Dados Sensíveis
- Limitação de Taxa e Prevenção de Abusos
- Tratamento de Erros e Padrões de Resiliência
- Defendendo-se contra injeção de prompts