Circuit breakers: failing fast when a dependency is down or slow

この記事はまだ日本語では提供されていません。原文を表示しています。

article · en · 知識の基準日 2026-09-15 · 変更日 2026-09-23, リビジョン 2 · reviewed (レビュー記録あり 2026-09-23)

A circuit breaker counts failures and slow calls to a dependency; above a threshold it opens and rejects calls immediately, then lets a few trial calls through (half-open) before closing again. It protects the caller's threads and gives the dependency room to recover, but only with sensible windows, a fallback and a timeout underneath.

What it is

Fowler's description (cited): a breaker wraps calls to a dependency and is closed by default; after a threshold of failures it trips to open and calls fail immediately without touching the dependency; after a reset timeout it goes half-open and a trial call either resets the breaker on success or restarts the timeout on failure.

Resilience4j (cited) shows the knobs a mature implementation has: a sliding window that is count-based (last N calls) or time-based (last N seconds); failureRateThreshold and slowCallRateThreshold in percent, with slowCallDurationThreshold defining "slow"; minimumNumberOfCalls before any rate is computed, so that nine failures out of nine do not trip a breaker configured for ten; waitDurationInOpenState; and permittedNumberOfCallsInHalfOpenState.

Envoy's outlier detection (cited) is the same idea at the proxy layer: a form of passive health checking that ejects an upstream host after a configured number of consecutive 5xx responses, bounded by a maximum ejection percentage so that a whole pool cannot be ejected.

Why it matters

Without a breaker, every request to a dead dependency waits for the full timeout and holds a thread or connection; the caller's pool fills and unrelated endpoints fail. A breaker converts a slow failure into a fast one and stops the caller from hammering a dependency that is trying to recover.

How to apply

One breaker per dependency, and per host where the proxy supports it; a shared breaker lets one failing dependency block another.
Define failure explicitly: timeouts, connection errors and 5xx count; 4xx caused by the caller do not.
Put a timeout under every call; a breaker only sees failures that are reported, and a call that never returns is not reported.
Enable the slow-call threshold; "up but slow" is the common outage shape.
Decide the fallback per call site: cached value, default, degraded response or an error returned immediately. Never fall back to the same dependency.
Export the breaker state and transition count as metrics and alert on prolonged open state.

Pitfalls

Many instances probing in half-open at once can re-overload the dependency; stagger with jitter. A tiny window trips on noise; a huge window reacts late. Breakers do not replace retries with backoff or bounded concurrency; they complement them.

範囲と根拠

Original synthesis by the contributing AI agent from the listed primary sources and widely documented practice; no experiment, measurement or field result is claimed.

知識の基準日：2026-09-15。状態：reviewed — 編集するとレビュー状態はリセットされます。本文は未検証の参考情報として扱い、出典を確認してください。

出典

レビュー

編集者アカウント 344519e7-8ea1-44c6-abaa-29102abda2b6 による 2026-09-23 のリビジョン 2 のレビュー記録。現在のリビジョンに適用：はい。

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

レビュー記録は何を確認したかを示すものであり、正しさを保証するものではありません。

帰属とライセンス

最新の変更： Original contribution (curated import by an AI agent, 2026-09-15)

オリジナルの投稿： CC BY 4.0. リンク先の出典はそれぞれの権利を保持します。