Microservices Communication Patterns (Saga, Circuit Breaker) · Lektion

Circuit Breaker und Bulkhead

Lernen Sie, Circuit Breakers mit dem Bulkhead-Pattern zu kombinieren, um Ressourcenausfälle zu isolieren und Kaskadenprobleme zu verhindern.

Circuit Breaker und Bulkhead ist eine kostenlose Microservices Communication Patterns (Saga, Circuit Breaker)-Lektion auf CoddyKit. Dies ist Lektion 1 von 4. Du kannst die komplette Lektion unten kostenlos lesen – dann übst du sie direkt im Browser mit einem integrierten Code-Editor und einem KI-Tutor rund um die Uhr. Sie ist Teil des Microservices Communication Patterns (Saga, Circuit Breaker)-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der Microservices Communication Patterns (Saga, Circuit Breaker)-Kurs umfasst insgesamt 4 Lektionen.

Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.

Patterns Work Better Together

Resilience patterns like Circuit Breaker and Bulkhead are powerful on their own. But in complex microservices, combining them offers even stronger protection.

Think of it like different layers of security for your application. Each layer catches different types of threats, creating a more robust defense.

Circuit Breaker Refresher

Remember the Circuit Breaker pattern? It's like an electrical circuit for your service calls.

It monitors calls to a service.
If failures exceed a threshold, it 'opens' the circuit.
Once open, further calls fail immediately, preventing overload to the failing service and saving resources.
After a timeout, it 'half-opens' to test if the service has recovered.

Bulkhead Pattern Refresher

The Bulkhead pattern isolates resources. Imagine a ship with watertight compartments (bulkheads).

If one compartment floods, the others remain safe.
In microservices, this means separating resource pools (e.g., thread pools, connections) for different services.
A failure in one service's resource pool won't exhaust resources needed by other services.

Synergy: CB + Bulkhead

Why use both? They tackle different problems but complement each other perfectly.

Circuit Breaker: Focuses on stopping requests to a failing service.
Bulkhead: Focuses on isolating resources to prevent cascading failures due to resource exhaustion.

Together, they provide a comprehensive defense against various failure modes.

Bulkhead Helps Circuit Breaker

How does Bulkhead make Circuit Breaker better?

A Circuit Breaker needs to detect failures. If a service is overwhelmed (e.g., due to resource exhaustion) and all calls to it start failing slowly, it can take time for the Circuit Breaker to open.

By isolating resources, Bulkhead ensures that only a limited set of resources is consumed by a misbehaving service, preventing total exhaustion and allowing the Circuit Breaker to react more quickly and cleanly to actual service failures, rather than just resource starvation.

Circuit Breaker Helps Bulkhead

And how does Circuit Breaker enhance Bulkhead?

If a service is known to be failing (Circuit Breaker is OPEN), the Circuit Breaker will intercept requests and fail them immediately, before they even try to acquire a resource from the Bulkhead's pool.

This means the Bulkhead's limited resources are not wasted on calls destined to fail anyway, preserving them for other, potentially healthy, operations or for when the service recovers.

Real-World: Thread Pools

A common way to implement the Bulkhead pattern is using thread pools.

Assign a dedicated, limited thread pool to calls for a specific external service.
If that service is slow or unresponsive, only its dedicated threads get tied up.
Other services, with their own thread pools, remain unaffected.

When combined with a Circuit Breaker, the CB stops calls before they even enter the thread pool if the service is down.

Code: CB & BH in Action

This example shows how a Circuit Breaker (CB) check happens before a Bulkhead (BH) resource acquisition. If the CB is open, the call fails immediately, saving BH resources.

import java.util.concurrent.Semaphore;
import java.util.concurrent.atomic.AtomicBoolean;

public class Main {
    private static AtomicBoolean circuitOpen = new AtomicBoolean(false);
    private static long lastFailureTime = 0;
    private static final long RESET_TIMEOUT_MS = 5000;

    private static final Semaphore serviceBulkhead = new Semaphore(2);

    public static void callProtectedService(String callerId) {
        // 1. Circuit Breaker check (Fail Fast)
        if (circuitOpen.get()) {
            if (System.currentTimeMillis() - lastFailureTime > RESET_TIMEOUT_MS) {
                System.out.println(callerId + ": Circuit Half-Open. Testing service...");
                circuitOpen.set(false); // Simple reset for demo
            } else {
                System.out.println(callerId + ": CB OPEN. REJECTED!");
                return;
            }
        }

        // 2. Bulkhead check (Resource Isolation)
        boolean acquiredBulkhead = false;
        try {
            if (serviceBulkhead.tryAcquire()) {
                acquiredBulkhead = true;
                System.out.println(callerId + ": BH slot ACQUIRED. Calling...");
                Thread.sleep(200); // Simulate work

                if (callerId.equals("Call-3") || callerId.equals("Call-4")) {
                    System.out.println(callerId + ": Simulating FAILURE!");
                    circuitOpen.set(true);
                    lastFailureTime = System.currentTimeMillis();
                } else {
                    System.out.println(callerId + ": Call SUCCESS.");
                }
            } else {
                System.out.println(callerId + ": BH FULL. REJECTED!");
            }
        } catch (InterruptedException e) {
            Thread.currentThread().interrupt();
            System.out.println(callerId + ": Call interrupted.");
        } finally {
            if (acquiredBulkhead) {
                serviceBulkhead.release();
            }
        }
    }

    public static void main(String[] args) throws InterruptedException {
        System.out.println("--- First calls (CB CLOSED) ---");
        for (int i = 1; i <= 5; i++) {
            final int callNum = i;
            new Thread(() -> callProtectedService("Call-" + callNum)).start();
            Thread.sleep(50);
        }
        Thread.sleep(1500);

        System.out.println("\n--- Second calls (CB potentially OPEN) ---");
        for (int i = 6; i <= 10; i++) {
            final int callNum = i;
            new Thread(() -> callProtectedService("Call-" + callNum)).start();
            Thread.sleep(50);
        }
        Thread.sleep(6000);

        System.out.println("\n--- Third calls (after reset) ---");
        for (int i = 11; i <= 13; i++) {
            final int callNum = i;
            new Thread(() -> callProtectedService("Call-" + callNum)).start();
            Thread.sleep(50);
        }
    }
}

Combined Benefits

Using Circuit Breaker and Bulkhead together provides:

Enhanced Fault Isolation: Prevents a single failing service from taking down others, both by stopping calls and by limiting resource usage.
Improved Resource Management: Efficiently uses available resources, rejecting calls early if a service is known to be unhealthy.
Faster Recovery: Allows healthy parts of the system to continue functioning, aiding overall system stability and recovery.
Predictable Behavior: Helps maintain predictable response times and throughput under stress.

Quick Check

Which of the following statements accurately describe the benefits of combining the Circuit Breaker and Bulkhead patterns?

Recap: Stronger Together

In this lesson, we explored the powerful combination of the Circuit Breaker and Bulkhead patterns.

We saw how Circuit Breaker prevents calls to failing services.
We revisited how Bulkhead isolates resources.
Most importantly, we learned how they mutually enhance each other to create a more resilient and stable microservices architecture.

Next, we'll see how Circuit Breakers can be combined with Retry Logic for even more robust error handling!

Häufig gestellte Fragen

Ist die Lektion „Circuit Breaker und Bulkhead“ kostenlos?

Ja — der vollständige Text von „Circuit Breaker und Bulkhead“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des Microservices Communication Patterns (Saga, Circuit Breaker)-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der Microservices Communication Patterns (Saga, Circuit Breaker)-Kurs umfasst insgesamt 4 Lektionen.

Was lerne ich in „Circuit Breaker und Bulkhead“?

Lernen Sie, Circuit Breakers mit dem Bulkhead-Pattern zu kombinieren, um Ressourcenausfälle zu isolieren und Kaskadenprobleme zu verhindern. Du übst Microservices Communication Patterns (Saga, Circuit Breaker) mit praktischem Code, den du direkt im Browser ausführst, und ein 24/7 KI-Tutor beantwortet deine Fragen während du die Lektion bearbeitest.

Brauche ich Erfahrung, um Microservices Communication Patterns (Saga, Circuit Breaker) zu starten?

Keine Vorkenntnisse erforderlich. Microservices Communication Patterns (Saga, Circuit Breaker) auf CoddyKit ist für Anfänger bis fortgeschrittene Lernende strukturiert, sodass du hier starten oder von Anfang an beginnen und in deinem eigenen Tempo voranschreiten kannst. Dies ist Lektion 1 von 4.

Wie lange dauert die Lektion „Circuit Breaker und Bulkhead“?

Die meisten CoddyKit-Lektionen dauern etwa 5–10 Minuten. Jede ist kompakt und interaktiv, sodass du stetig Fortschritte machst und genau dort weitermachst, wo du aufgehört hast – im Web und in der App.

Kann ich in dieser Microservices Communication Patterns (Saga, Circuit Breaker)-Lektion Code schreiben und ausführen?

Ja. Jede Microservices Communication Patterns (Saga, Circuit Breaker)-Lektion enthält einen integrierten Code-Editor, sodass du echten Code direkt in deinem Browser schreibst und ausführst und sofort KI-Feedback erhältst — ohne lokale Einrichtung erforderlich.

Alle Lektionen in diesem Kurs

← Zurück zu Microservices Communication Patterns (Saga, Circuit Breaker)