RPC

Deadline Propagation Preserves Timeout Budgets Across RPC Hops

Deadline Propagation Preserves Timeout Budgets Across RPC Hops A timeout that restarts at every service boundary can turn a short caller budget into a much longer chain of work. A client may allow 800 milliseconds, service A may spend 500 milliseconds locally, then call service B with a fresh 800-millisecond timeout. B can continue working long after the client has stopped waiting. Deadline propagation keeps one end time attached to the request. Each hop derives its remaining budget from that deadline and refuses to start work that cannot fit within it. The result is not faster execution by itself. It is bounded execution that respects the time contract established upstream.