hop
One step a request takes between two machines or programs on its way to the final server.
In more detail
Each hop through a gateway, proxy or service adds latency and another place to fail. Measuring time at each hop shows where latency accumulates.
Related terms
- API gateway — A server that sits in front of one or more services and handles shared concerns such as routing, authentication, rate limits and TLS for every request.
- latency — The time between asking for something and getting the answer back.
- latency budget — A latency target divided among the hops a request makes, so each part knows how much time it may spend.
- round trip — One journey of a request to a server and its response back, whose time adds directly to how long the caller waits.
- deadline — The point in time by which a request must finish, after which its answer is no longer useful.
Taught in
- API Gateways And Proxies — Modern API Architecture: REST, GraphQL & gRPC
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Latency Numbers Every Engineer Should Know — Scalable System Design & Distributed Architecture
- Eventual Consistency And What It Costs A Product — Scalable System Design & Distributed Architecture
- Caching Strategies And Topology — Scalable System Design & Distributed Architecture
- Timeouts, And Avoiding Cascaded Failure — Scalable System Design & Distributed Architecture
- Observability As A Design Input — Scalable System Design & Distributed Architecture