Timeout
Also called: request timeout, deadline, time budget
A timeout limits how long an operation may wait; a deadline specifies the point in time after which its result is no longer wanted. Protocol clients use these limits to bound resource use and latency. Connection establishment, reading a response and completing an entire operation can have different limits.
Suppose a checkout request has a two-second budget. If earlier work consumes 1.5 seconds, a downstream call should receive the remaining budget rather than another full two seconds. Expiry tells the caller to stop waiting, not that remote side effects never occurred. Cancellation can reduce wasted work, but the server application must cooperate and already completed work is not automatically undone.
- Related
- Retry backoff and jitter, Idempotency key, gRPC
- Further reading