request path
The work a system does between receiving a request and sending the answer the user is waiting for.
In more detail
Keep only what the answer depends on in the request path; consequences such as thumbnails, email and indexing belong behind a queue. The work does not disappear, it just stops adding to user latency.
Related terms
- asynchronous — Describes work that starts now and finishes later, letting the program do other things instead of waiting for it.
- message queue — A store that holds messages from producers until consumers are ready to process them, decoupling the rate of arrival from the rate of work.
- latency budget — A latency target divided among the hops a request makes, so each part knows how much time it may spend.
Taught in
- Latency Numbers Every Engineer Should Know — Scalable System Design & Distributed Architecture
- The Storage Decision: Key Value, Search And Blob — Scalable System Design & Distributed Architecture
- Queues, Events And Asynchronous Work — Scalable System Design & Distributed Architecture
- Timeouts, And Avoiding Cascaded Failure — Scalable System Design & Distributed Architecture
- Monolith Versus Services: The Honest Trade Offs — Scalable System Design & Distributed Architecture