deadline
The point in time by which a request must finish, after which its answer is no longer useful.
In more detail
Every request needs one, because a worker waiting forever cannot serve anyone else. The caller owns the total budget and passes the absolute deadline to each dependency, which stops work once it has passed.
Related terms
- timeout — A limit on how long a caller waits for an answer before giving up.
- deadline propagation — Passing a request's absolute deadline to every service it calls, so each knows how much time is left.
- cancellation — Stopping work that is no longer needed, such as a search request made obsolete by a new keystroke.
- latency budget — A latency target divided among the hops a request makes, so each part knows how much time it may spend.
Taught in
- When The Call Fails — AI Engineering: LLM Apps, RAG & Agents
- Latency Numbers Every Engineer Should Know — Scalable System Design & Distributed Architecture
- Timeouts, And Avoiding Cascaded Failure — Scalable System Design & Distributed Architecture
- Retries, Backoff And Jitter — Scalable System Design & Distributed Architecture
- Backpressure And Load Shedding — Scalable System Design & Distributed Architecture
- Observability As A Design Input — Scalable System Design & Distributed Architecture