Every external call needs a timeout, every timeout needs a fallback — resilience patterns for HTTP, databases, and third-party services
88
90%
Does it follow best practices?
Impact
85%
4.72xAverage score across 5 eval scenarios
Passed
No known issues
timeouts-on-all-service-calls
0%
100%
critical-vs-supplementary-handling
93%
100%
supplementary-fetched-independently
91%
100%
fallback-for-ads-service
100%
100%
fallback-for-notifications
100%
100%
retry-critical-services
0%
100%
structured-failure-logging
0%
70%
circuit-breaker-implemented
0%
100%
warnings-in-response
0%
0%
timeouts-on-all-service-calls
0%
100%
per-dependency-timeouts
0%
50%
supplementary-services-independent
53%
100%
partial-response-when-supplementary-fails
80%
100%
required-vs-optional-distinction
100%
100%
warnings-for-failed-services
0%
0%
structured-failure-logging
0%
90%
retry-logic-present
0%
100%
circuit-breaker-considered
0%
100%
timeouts-on-all-service-calls
13%
100%
fallback-for-user-profile
46%
100%
fallback-for-catalog-enrichment
0%
100%
retry-with-exponential-backoff
0%
0%
only-transient-errors-retried
0%
0%
circuit-breaker-pattern
0%
100%
per-dependency-timeout-values
12%
0%
structured-failure-logging
0%
90%
error-handling-does-not-leak
87%
75%
timeouts-on-all-fetches
0%
100%
parallel-with-isolation
0%
100%
partial-results-returned
0%
100%
fallback-values-per-provider
0%
100%
warnings-for-unavailable-providers
0%
100%
structured-error-logging
0%
70%
retry-with-backoff-on-transient
0%
100%
per-provider-timeout-config
0%
0%
circuit-breaker-for-providers
0%
100%
timeouts-on-all-fetches
0%
100%
independent-error-handling
0%
100%
partial-response-on-failure
0%
100%
fallback-values-for-failed-services
0%
100%
warnings-field-in-response
0%
100%
structured-error-logging
0%
100%
retry-with-backoff
0%
100%
circuit-breaker-or-failure-tracking
0%
100%
per-service-timeout-config
0%
28%