Microservices Communication Patterns (Saga, Circuit Breaker) · レッスン

サーキットブレーカーとバルクヘッド

サーキットブレーカーとバルクヘッドパターンを組み合わせ、リソース障害を分離して連鎖的な問題を防ぐ方法を学習します。

レッスン 1/411 ステップ

「サーキットブレーカーとバルクヘッド」はCoddyKit上の無料Microservices Communication Patterns (Saga, Circuit Breaker)レッスンです。これはレッスン1/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはMicroservices Communication Patterns (Saga, Circuit Breaker)学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Microservices Communication Patterns (Saga, Circuit Breaker)コースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

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!

無料で開始

AI チューターと学ぶ Microservices Communication Patterns (Saga, Circuit Breaker) — 無料

ブラウザでリアルコードを書いて実行し、24/7 の AI チューターから瞬時にサポートを受け、ウェブまたはアプリで続きから学習できます。

コース: 12
レッスン: 48

無料で学習を始めるコース全体を表示

よくある質問

「サーキットブレーカーとバルクヘッド」レッスンは無料ですか？

はい。「サーキットブレーカーとバルクヘッド」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Microservices Communication Patterns (Saga, Circuit Breaker)コースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Microservices Communication Patterns (Saga, Circuit Breaker)コースには全4レッスンが含まれています。

「サーキットブレーカーとバルクヘッド」で何を学びますか？

サーキットブレーカーとバルクヘッドパターンを組み合わせ、リソース障害を分離して連鎖的な問題を防ぐ方法を学習します。ブラウザで直接実行するハンズオンコードでMicroservices Communication Patterns (Saga, Circuit Breaker)を演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Microservices Communication Patterns (Saga, Circuit Breaker)を始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのMicroservices Communication Patterns (Saga, Circuit Breaker)は初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン1/4です。

「サーキットブレーカーとバルクヘッド」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このMicroservices Communication Patterns (Saga, Circuit Breaker)レッスンでコードを書いて実行できますか？

はい。すべてのMicroservices Communication Patterns (Saga, Circuit Breaker)レッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Microservices Communication Patterns (Saga, Circuit Breaker)に戻る