Many clerks opening the same health page would each trigger the same expensive DNA Center query. Which consumer design protects latency and the platform quota?
Select an answer to reveal the explanation.
Short Explanation
If fifty people ask “is the bridge open?” you call the bridge once and share the answer—you do not dial fifty times. Back-end coalesce and throttle beat “retry harder from every tab.” Amplifying load hurts latency and quota.
Full Explanation
When many UI users would each trigger the same expensive controller query, a back-end throttle or coalesced refresh protects both latency and the platform quota. Retrying harder from every browser tab is the wrong design. Stay at consumer design; do not turn this into unrecoverable-error control-flow coding.