Reliability & operations · Glossary term
What is Deadline Propagation?
Passing the remaining end-to-end time budget to downstream calls so each dependency knows how long the original request can still usefully wait.
Why does Deadline Propagation matter?
Independent timeouts can exceed the user's deadline and leave abandoned work consuming capacity after the result is no longer useful.
Deadline Propagation in practice
Set one request deadline at ingress, subtract elapsed time for each downstream call, cancel expired work, and record which boundary exhausted the budget.
What is the common confusion about Deadline Propagation?
A deadline is an absolute or remaining completion boundary. A retry delay controls when another attempt begins and must fit inside that same budget.
Learn Deadline Propagation in the course
No lesson links to this term yet. Search the course catalog for it.
Related terms
- Retry with BackoffRepeating a failed transient operation after progressively longer delays, usually with randomized jitter and a strict retry limit.
- Retry BudgetA bound on retry traffic, usually expressed relative to original requests or over a time window, that prevents retries from consuming…
- Tail LatencyThe latency experienced by the slowest portion of requests, commonly summarized with a high percentile under a stated workload and time…
- Service Level Objective (SLO)A target range or threshold for a service-level indicator over a stated population and measurement window.
Sources
More terms in Reliability & operations
This entry comes from glossary/terms.md on GitHub. Browse all 250 glossary terms.