A Python permit service calling a third-party address validator fails the whole submit when the vendor blips for two seconds. Which resilience approach should developers apply in application code?
Select an answer to reveal the explanation.
Short Explanation
A two-second hiccup from the address vendor should not trash the whole permit like a blown fuse. Put a timeout on the call, retry with backoff, and degrade gracefully if it is still down. That is resilient application code.
Full Explanation
Fault-tolerant integrations combine bounded timeouts, retries with exponential backoff (often with jitter), and graceful degradation or alternate paths when a dependency stays unhealthy. Waiting forever holds resources; failing on the first blip and single immediate retries amplify outages. DVA-C02 expects developers to implement these patterns in application code for third-party calls.