Microservices Communication Patterns (Saga, Circuit Breaker) · 课时

熔断器与重试逻辑

了解熔断器与重试机制之间的相互作用，从而优化错误处理和恢复。

熔断器与重试逻辑 是 CoddyKit 上的免费 Microservices Communication Patterns (Saga, Circuit Breaker) 课时。这是第 2 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Microservices Communication Patterns (Saga, Circuit Breaker) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Microservices Communication Patterns (Saga, Circuit Breaker) 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Combining Circuit Breaker & Retry

In distributed systems, failures are inevitable. We've learned about the Retry Pattern for transient issues and the Circuit Breaker for persistent ones.

But how do these powerful patterns work together? Combining them effectively is key to building truly resilient microservices.

Recap: The Retry Pattern

The Retry Pattern automatically re-attempts an operation that has failed due to a temporary, transient error.

Use case: Network glitches, temporary service unavailability, database deadlocks.
Goal: Overcome momentary hiccups without user intervention.
Mechanism: Usually involves a delay between retries (e.g., exponential backoff).

Recap: The Circuit Breaker

A Circuit Breaker prevents an application from repeatedly invoking a service that is likely to fail. It "trips" the circuit to stop calls when too many errors occur.

Use case: Service is down, overloaded, or consistently returning errors.
Goal: Fail fast, prevent cascading failures, give the failing service time to recover.
States: Closed, Open, Half-Open.

Synergy: CB and Retry

Imagine a service experiencing a brief network blip. Retry can handle this gracefully. But what if the service is completely offline for an extended period?

Without a Circuit Breaker, retries would continuously hammer the unresponsive service, wasting resources and prolonging the problem. This is where their combined power shines!

Order of Operations

When combining these patterns, a critical design decision is: which one wraps the other?

Does the Retry Pattern wrap the Circuit Breaker, or does the Circuit Breaker wrap the Retry Pattern?

The order significantly impacts how your system responds to different types of failures.

Retry Wrapping Circuit Breaker

If the Retry Pattern wraps the Circuit Breaker:

Retry attempts the operation.
The Circuit Breaker is engaged.
If the CB opens, the first attempt fails, and retry might try again, hitting the already open CB.
This can lead to retries hitting a fast-failing CB, not allowing the CB to fully protect the system initially.

This setup is generally less effective.

Circuit Breaker Wrapping Retry

If the Circuit Breaker wraps the Retry Pattern:

The Circuit Breaker monitors the entire retry operation.
If the initial call fails, retry attempts again.
Only if all retries fail within the configured attempts, does the Circuit Breaker count it as a single failure.
If enough such "all-retry-failed" attempts occur, the CB opens.

This is the recommended approach.

CB Protecting Retry Logic

Here's a conceptual Java example showing how a Circuit Breaker would wrap an operation that includes retry logic. Notice the Circuit Breaker's decision to open or close is based on the final outcome of the retried call.

Try running this example:

import java.util.concurrent.atomic.AtomicInteger;

public class Main {
    // Simulate a dependency that sometimes fails
    private static AtomicInteger serviceCallCount = new AtomicInteger(0);

    public static boolean unreliableServiceCall() {
        System.out.println("  Attempting service call...");
        int currentCount = serviceCallCount.incrementAndGet();
        if (currentCount % 3 == 0) { // Fails every 3rd call
            System.out.println("  Service call FAILED temporarily.");
            return false;
        }
        System.out.println("  Service call SUCCESS.");
        return true;
    }

    public static boolean executeWithRetry() {
        int maxRetries = 2;
        long delayMillis = 100;
        for (int i = 0; i <= maxRetries; i++) {
            try {
                if (unreliableServiceCall()) {
                    return true; // Success after retry
                }
            } catch (Exception e) {
                // Log exception, continue retry
            }
            if (i < maxRetries) {
                System.out.println("  Retrying in " + delayMillis + "ms...");
                try { Thread.sleep(delayMillis); } catch (InterruptedException e) { Thread.currentThread().interrupt(); }
            }
        }
        return false; // All retries failed
    }

    // Conceptual Circuit Breaker logic for demonstration
    private static boolean circuitOpen = false;
    private static int failureCount = 0;
    private static final int FAILURE_THRESHOLD = 2; // Open after 2 consecutive failures
    private static final long RESET_TIMEOUT_MILLIS = 500; // Try to close after 0.5s
    private static long lastFailureTime = 0;

    public static boolean executeWithCircuitBreakerAndRetry() {
        if (circuitOpen) {
            if (System.currentTimeMillis() - lastFailureTime > RESET_TIMEOUT_MILLIS) {
                System.out.println("Circuit Breaker: Attempting HALF-OPEN state...");
                circuitOpen = false; // Move to half-open (for demo, just close)
                failureCount = 0; // Reset count
            } else {
                System.out.println("Circuit Breaker: OPEN! Failing fast.");
                return false; // Fail fast if open
            }
        }

        boolean success = executeWithRetry(); // Execute the retry logic

        if (!success) {
            failureCount++;
            lastFailureTime = System.currentTimeMillis();
            if (failureCount >= FAILURE_THRESHOLD) {
                circuitOpen = true;
                System.out.println("Circuit Breaker: OPENED due to repeated failures!");
            } else {
                System.out.println("Circuit Breaker: Failure detected, count=" + failureCount);
            }
        } else {
            failureCount = 0; // Reset failure count on success
            System.out.println("Circuit Breaker: Success, failure count reset.");
        }
        return success;
    }

    public static void main(String[] args) {
        System.out.println("--- Scenario: CB wrapping Retry ---");
        for (int i = 0; i < 7; i++) { // Simulate multiple requests
            System.out.println("\nRequest " + (i + 1) + ":");
            boolean overallSuccess = executeWithCircuitBreakerAndRetry();
            System.out.println("Overall result for Request " + (i + 1) + ": " + (overallSuccess ? "SUCCESS" : "FAILURE"));
            try { Thread.sleep(100); } catch (InterruptedException e) { Thread.currentThread().interrupt(); }
        }
    }
}

Why This Order is Best

Placing the Circuit Breaker around the Retry Pattern offers several advantages:

Efficient Failure Detection: The CB only opens after a series of genuinely failed operations (i.e., all retries failed), distinguishing transient issues from persistent outages.
Reduced Load: Once the CB is open, it prevents any further retry attempts, protecting the downstream service from being overwhelmed during a prolonged failure.
Faster Failures: When the service is truly down, the CB opens quickly, allowing your application to fail fast instead of waiting for all retries to exhaust.

Check Your Understanding

Consider a microservice that experiences intermittent network glitches (transient failures) and occasionally goes completely offline for maintenance (persistent failures).

You are implementing both the Retry Pattern and the Circuit Breaker Pattern to handle these scenarios. Which setup is generally recommended for optimal resilience?

Lesson Summary

We've explored the powerful synergy between the Circuit Breaker and Retry Patterns. While both enhance resilience, their combined effectiveness hinges on their interaction.

Remember, the best practice is to have the Circuit Breaker wrap the Retry Pattern. This allows retries to handle transient faults, while the Circuit Breaker steps in to protect against persistent failures, preventing cascading issues and improving overall system stability.

Keep building robust systems!

常见问题解答

「熔断器与重试逻辑」课时是免费的吗？

是的 — 「熔断器与重试逻辑」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Microservices Communication Patterns (Saga, Circuit Breaker) 课程的其余内容，请升级到 CoddyKit PRO。 Microservices Communication Patterns (Saga, Circuit Breaker) 课程共包含 4 节课。

「熔断器与重试逻辑」这节课中我会学到什么？

了解熔断器与重试机制之间的相互作用，从而优化错误处理和恢复。你通过在浏览器中直接运行的动手代码来练习 Microservices Communication Patterns (Saga, Circuit Breaker)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Microservices Communication Patterns (Saga, Circuit Breaker) 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Microservices Communication Patterns (Saga, Circuit Breaker) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 2 节课，共 4 节。

「熔断器与重试逻辑」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Microservices Communication Patterns (Saga, Circuit Breaker) 课中编写并运行代码吗？

能。每节 Microservices Communication Patterns (Saga, Circuit Breaker) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Microservices Communication Patterns (Saga, Circuit Breaker)