sequence·OMG UML 2.5.1·software, infrastructure·complexity 3/3·since v0.5.1
Retry, timeout, and circuit breaker
UML sequence diagram for a gateway calling a payment service through a circuit breaker, with retry attempts, timeout handling, a break fragment for an open breaker, and an asynchronous fallback event.
For the distributed-systems engineer
sequence·§ —
↘ preview
100%
UTF-8 · LF · 30 lines · 876 chars✓ parsed·1.4 ms·10.7 KB SVG
Scenario
A checkout API must protect itself from a slow or failing payment provider. The diagram makes the resilience policy reviewable: the gateway checks the breaker, retries bounded attempts, records timeouts, and falls back to asynchronous recovery instead of blocking the customer forever.
Annotation key
loop (1,3)documents the bounded retry policy.altseparates fast responses, timeouts, and open-breaker rejection.break [authorized]exits the retry loop once a successful authorization arrives.->>marks asynchronous fallback work queued outside the request path.