A dashboard aggregates three municipal APIs, and one slow dependency should not blank the entire page. Which resilience approach should the developer apply?
Select an answer to reveal the explanation.
Short Explanation
If one streetlight sensor is offline, the whole city map shouldn't go black. Timeout and degrade that panel while the other two APIs still render. One global fail-together timeout, no timeouts at all, or abort-on-first-error are how one slow neighbor blanks the dashboard.
Full Explanation
Resilient aggregation isolates dependency failures using per-call timeouts, partial UI responses, and patterns such as circuit breakers so one slow or failing API does not deny the entire page. Shared all-or-nothing timeouts, unbounded waits, and serial abort-on-first-error couple the UX to the weakest dependency.