0Pricing
Microservices Communication Patterns (Saga, Circuit Breaker) · Leçon

Intégration aux appels de services

Intégrez des coupe-circuits à vos microservices pour encapsuler les appels à des services externes et vous protéger contre les défaillances.

Intégration aux appels de services est une leçon Microservices Communication Patterns (Saga, Circuit Breaker) gratuite sur CoddyKit. Ceci est la leçon 3 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Microservices Communication Patterns (Saga, Circuit Breaker), et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Microservices Communication Patterns (Saga, Circuit Breaker) comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

Wrap Up Your Calls!

Welcome to the final lesson on implementing Circuit Breakers! Today, we'll get hands-on and learn how to integrate a circuit breaker directly into your microservice's external calls.

Protecting these calls is crucial for building resilient systems that can gracefully handle failures and maintain responsiveness, even when dependencies are struggling.

Direct Service Calls

Imagine your service needs data from another microservice. A common way to do this is a direct method call or HTTP request. But what happens if that external service is slow or down?

Let's look at a basic setup without any protection.

import java.util.concurrent.ThreadLocalRandom;

class ExternalService {
  public String getData() throws Exception {
    System.out.println("ExternalService: Attempting to get data...");
    // Simulate success for now
    return "Data from external service";
  }
}

public class Main {
  public static void main(String[] args) {
    ExternalService service = new ExternalService();
    try {
      String result = service.getData();
      System.out.println("Result: " + result);
    } catch (Exception e) {
      System.err.println("Error: " + e.getMessage());
    }
  }
}

Simulating Service Failure

In the real world, external services aren't always perfect. They can fail due to network issues, overload, or bugs. Let's update our ExternalService to simulate these failures randomly.

Run the code a few times. You'll see how a single failure can break our Main application.

import java.util.concurrent.ThreadLocalRandom;

class ExternalService {
  private int callCount = 0;

  public String getData() throws Exception {
    callCount++;
    System.out.println("ExternalService: Call #" + callCount);
    // Simulate failure 50% of the time
    if (ThreadLocalRandom.current().nextDouble() < 0.5) {
      throw new RuntimeException("Simulated External Service Failure!");
    }
    return "Data from external service (call #" + callCount + ")";
  }
}

public class Main {
  public static void main(String[] args) {
    ExternalService service = new ExternalService();
    for (int i = 0; i < 3; i++) {
      System.out.println("--- Attempt " + (i + 1) + " ---");
      try {
        String result = service.getData();
        System.out.println("Result: " + result);
      } catch (Exception e) {
        System.err.println("Error: " + e.getMessage());
      }
      System.out.println();
      try { Thread.sleep(200); } catch (InterruptedException e) { Thread.currentThread().interrupt(); }
    }
  }
}

The Circuit Breaker Wrapper

This is where the Circuit Breaker comes in! Instead of calling the external service directly, we 'wrap' the call with our circuit breaker.

The circuit breaker then manages the call, decides if it should even be attempted (if the circuit is open), and handles failures. Here's a very simplified version of how such a wrapper might look:

import java.util.concurrent.Callable;

class MyCircuitBreaker {
  // In a real CB, this would manage state (open, closed, half-open)
  // and apply thresholds. For this lesson, we focus on the integration.
  public <T> T execute(Callable<T> primaryCall) throws Exception {
    try {
      System.out.println("CB: Executing primary call...");
      return primaryCall.call(); // Attempt the actual service call
    } catch (Exception e) {
      // A real CB would update its state here (e.g., trip the circuit)
      System.err.println("CB: Primary call failed: " + e.getMessage());
      throw e; // Re-throw for now, we'll add fallback later
    }
  }
}

Basic CB Integration

Now let's use our basic MyCircuitBreaker to wrap the calls to our unreliable ExternalService. Notice how the Main method now uses the circuit breaker's execute method.

Run this code. While it still shows errors, the circuit breaker is now involved in mediating the calls.

import java.util.concurrent.Callable;
import java.util.concurrent.ThreadLocalRandom;

// --- MyCircuitBreaker (Simplified) ---
class MyCircuitBreaker {
  public <T> T execute(Callable<T> primaryCall) throws Exception {
    try {
      System.out.println("CB: Executing primary call...");
      return primaryCall.call();
    } catch (Exception e) {
      System.err.println("CB: Primary call failed: " + e.getMessage());
      throw e;
    }
  }
}

// --- ExternalService (from previous scene) ---
class ExternalService {
  private int callCount = 0;

  public String getData() throws Exception {
    callCount++;
    System.out.println("ExternalService: Call #" + callCount);
    if (ThreadLocalRandom.current().nextDouble() < 0.5) {
      throw new RuntimeException("Simulated External Service Failure!");
    }
    return "Data from external service (call #" + callCount + ")";
  }
}

// --- Main Application ---
public class Main {
  public static void main(String[] args) {
    ExternalService service = new ExternalService();
    MyCircuitBreaker circuitBreaker = new MyCircuitBreaker();

    for (int i = 0; i < 3; i++) {
      System.out.println("--- Attempt " + (i + 1) + " ---");
      try {
        String result = circuitBreaker.execute(
          () -> service.getData() // The operation to protect
        );
        System.out.println("Result: " + result);
      } catch (Exception e) {
        System.err.println("Main: Caught error after CB: " + e.getMessage());
      }
      System.out.println();
      try { Thread.sleep(200); } catch (InterruptedException e) { Thread.currentThread().interrupt(); }
    }
  }
}

Graceful Failure: Fallbacks

Catching errors is good, but what if we could provide a default or alternative response when the primary service call fails or the circuit is open? This is where fallbacks come in.

  • A fallback is a predefined action or value that gets returned when the main operation cannot complete successfully.
  • It helps maintain a good user experience by preventing total outages and providing partial functionality.
  • Think of it as a 'plan B' for your service calls.

Implementing Fallback Logic

We'll enhance our MyCircuitBreaker to accept a second Callable: the fallback operation. If the primaryCall fails, the fallbackCall will be executed instead.

This makes our circuit breaker much more useful for handling failures gracefully.

import java.util.concurrent.Callable;

class MyCircuitBreaker {
  public <T> T execute(Callable<T> primaryCall, Callable<T> fallbackCall) {
    try {
      System.out.println("CB: Executing primary call...");
      return primaryCall.call();
    } catch (Exception e) {
      System.err.println("CB: Primary call failed. Invoking fallback: " + e.getMessage());
      try {
        // If primary fails, invoke the fallback
        return fallbackCall.call();
      } catch (Exception fallbackE) {
        System.err.println("CB: Fallback call also failed: " + fallbackE.getMessage());
        return null; // Or throw a specific exception if fallback is critical
      }
    }
  }
}

Putting It All Together

Now, let's see the full picture. We'll use our updated MyCircuitBreaker with both the primary service call and a simple fallback message.

Run this code multiple times. When the ExternalService fails, you'll now get the fallback message instead of an error in your Main application!

import java.util.concurrent.Callable;
import java.util.concurrent.ThreadLocalRandom;

// --- MyCircuitBreaker (with Fallback) ---
class MyCircuitBreaker {
  public <T> T execute(Callable<T> primaryCall, Callable<T> fallbackCall) {
    try {
      System.out.println("CB: Executing primary call...");
      return primaryCall.call();
    } catch (Exception e) {
      System.err.println("CB: Primary call failed. Invoking fallback: " + e.getMessage());
      try {
        return fallbackCall.call();
      } catch (Exception fallbackE) {
        System.err.println("CB: Fallback call also failed: " + fallbackE.getMessage());
        return null;
      }
    }
  }
}

// --- ExternalService (with failures) ---
class ExternalService {
  private int callCount = 0;

  public String getData() throws Exception {
    callCount++;
    System.out.println("ExternalService: Call #" + callCount);
    if (ThreadLocalRandom.current().nextDouble() < 0.5) {
      throw new RuntimeException("Simulated External Service Failure!");
    }
    return "Data from external service (call #" + callCount + ")";
  }
}

// --- Main Application ---
public class Main {
  public static void main(String[] args) {
    ExternalService service = new ExternalService();
    MyCircuitBreaker circuitBreaker = new MyCircuitBreaker();

    System.out.println("Attempting to fetch data with Circuit Breaker and Fallback:");

    for (int i = 0; i < 5; i++) {
      System.out.println("--- Attempt " + (i + 1) + " ---");
      String result = circuitBreaker.execute(
        () -> service.getData(), // Primary operation
        () -> "Fallback: Service is currently unavailable." // Fallback operation
      );
      System.out.println("Result: " + result);
      System.out.println();
      try { Thread.sleep(200); } catch (InterruptedException e) { Thread.currentThread().interrupt(); }
    }
  }
}

Strategic Integration Points

Where exactly should you place circuit breakers in your architecture?

  • Service Clients: Wrap all calls made from your service to other external services. This is the most common place.
  • API Gateways: If you use an an API Gateway, it's an excellent place to implement circuit breakers for calls to downstream microservices, protecting your frontend from direct service failures.
  • Dedicated Proxy Layers: For very complex systems, a dedicated proxy or sidecar pattern can manage circuit breakers transparently for all outbound calls.

Integrating Circuit Breakers

You've learned how to wrap external service calls with a Circuit Breaker. Let's check your understanding.

Lesson Summary

Great job! In this lesson, you've learned the practical steps of integrating a circuit breaker into your microservice calls. We covered:

  • The risks of unprotected external service calls.
  • How to 'wrap' a service call using a circuit breaker's execute method.
  • The importance and implementation of fallback operations for graceful degradation.
  • Common strategic points in your architecture for integrating circuit breakers.

By applying these techniques, you can significantly enhance the resilience and stability of your distributed systems. Keep practicing!

Questions Fréquemment Posées

La leçon « Intégration aux appels de services » est-elle gratuite ?

Oui — le texte complet de « Intégration aux appels de services » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Microservices Communication Patterns (Saga, Circuit Breaker), passe à CoddyKit PRO. Le cours Microservices Communication Patterns (Saga, Circuit Breaker) comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Intégration aux appels de services » ?

Intégrez des coupe-circuits à vos microservices pour encapsuler les appels à des services externes et vous protéger contre les défaillances. Tu pratiques Microservices Communication Patterns (Saga, Circuit Breaker) avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer Microservices Communication Patterns (Saga, Circuit Breaker) ?

Aucune expérience préalable n'est requise. Microservices Communication Patterns (Saga, Circuit Breaker) sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 3 sur 4.

Combien de temps prend la leçon « Intégration aux appels de services » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon Microservices Communication Patterns (Saga, Circuit Breaker) ?

Oui. Chaque leçon Microservices Communication Patterns (Saga, Circuit Breaker) inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

  1. Choix d’une bibliothèque de coupe-circuit
  2. Configuration des instances de coupe-circuit
  3. Intégration aux appels de services
  4. Ajouter des replis aux disjoncteurs
← Retour à Microservices Communication Patterns (Saga, Circuit Breaker)