Protocols
Saved & recent

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
2-second overall budget 1.5 s already spent 0.5 s left caller remote operation caller waits deadline wait ends already completed illustrative timing
A hypothetical two-second budget leaves only half a second after 1.5 seconds of earlier work. Timeout limits waiting, not prior effects.

View in the full Protocols collection