Skip to main content

Circuit Breaker Explorer

Use the stage controls to compare the synthetic input, authored output, and configuration at each step.

How to use this explorer

Move between stages with the arrows or the numbered stage list. Each stage shows the input it receives on the left and the output it produces on the right, with the lines that changed marked. The configuration that makes the change sits below the comparison, and the final stage shows the complete pipeline.

The 4 stages in order

  1. No Circuit Breakers
    Authored requests before timeout, catch, or fallback configuration is added.
  2. HTTP Circuit Breakers
    Add the example HTTP timeout and retry settings, then route processor errors through a catch branch.
  3. Database Circuit Breakers
    Add authored connection and query bounds around the SQL branch. Runtime database behavior is not exercised.
  4. Multi-Level Fallback
    Illustrate primary, secondary, local-buffer, and rejected-record branches without asserting their runtime availability or durability.

Interactive pipeline

CIRCUIT BREAKER PATTERNS

Downstream call and fallback configuration

Stage 1 of 4

No Circuit Breakers

Authored requests before timeout, catch, or fallback configuration is added.

2HighlightsAuthored emphasis only—not a computed diff.
Copy & download

Input

{"sensor_id": "temp-001","value": 72.5,"timestamp": "2024-01-15T10:00:00Z"}

Output

Authored highlight: ❌ Request Status:timeout after 60sretrying... timeout after 60sretrying... timeout after 60sAuthored highlight: ❌ Pipeline Status:pending_requests: 5000+memory_state: authored_highpipeline: BACKING UP
Partial snippet01-no-circuit-breakers.yaml
output:
  # No timeouts, no retries, no fallbacks
  http_client:
    url: https://api.external.com/process
    # ❌ No timeout - waits forever
    # ❌ No retry limit - infinite retries
    # ❌ No fallback - total failure