Deadlines

Deadline Propagation Stops Expired Requests from Consuming Downstream Capacity

A timeout placed only at the outer edge of a request does not automatically limit the work started deeper in the call graph. The client may stop waiting after 800 milliseconds while an internal service continues a database query, a remote call, or a queued task for several more seconds. The response is already useless to that client, yet the system is still spending capacity on it. Deadline propagation carries the request’s time boundary with the work. Each component can compare that boundary with its current clock, reserve time for its own processing, and refuse or cancel work that no longer fits. The result is not merely faster failure. It is a tighter relationship between useful work and resource consumption.