How should failed external geocoding calls be handled to maintain resilience?

How should failed external geocoding calls be handled to maintain resilience?

• A. Immediately abort and return an error without retries.
• B. Implement retries with backoff, fall back to last-known coordinates if available, cache results, and surface clear, actionable error messages to the user.
• C. Switch to a different external service without backoff.
• D. Ignore errors and proceed with an empty coordinate.

Answer: (B)

Resilience when an external geocoding service fails. The best approach is to retry with backoff, so transient issues don’t cause immediate disruption and the system can recover without overwhelming the service. If you have a last known set of coordinates, fall back to them to keep the user moving and maintain functionality even during outages. Caching results helps reduce repeated calls, improve performance, and lessen the load on the external service. Finally, surface clear, actionable error messages so users understand what happened and what to expect next, enabling better handling on the client side (e.g., a retry later or using the last-known data). This combination provides continuity, responsiveness, and transparency. The other options either end the process too early, ignore systemic issues, or risk repeated failures without a graceful degradation.

Resilience when an external geocoding service fails. The best approach is to retry with backoff, so transient issues don’t cause immediate disruption and the system can recover without overwhelming the service. If you have a last known set of coordinates, fall back to them to keep the user moving and maintain functionality even during outages. Caching results helps reduce repeated calls, improve performance, and lessen the load on the external service. Finally, surface clear, actionable error messages so users understand what happened and what to expect next, enabling better handling on the client side (e.g., a retry later or using the last-known data). This combination provides continuity, responsiveness, and transparency. The other options either end the process too early, ignore systemic issues, or risk repeated failures without a graceful degradation.