Product → API Products
Request-Response
A communication pattern where one party sends a request and waits for a corresponding response.
Motivation
Request-Response is useful because it gives engineers a precise handle on a recurring problem: a communication pattern where one party sends a request and waits for a corresponding response.. It helps you decide what to pay attention to, what abstractions are available, and which tradeoffs matter in real systems.
Where it fits
Request-Response belongs to the Product track, inside the API Products layer. In the knowledge graph, this places it near concepts that explain the same level of abstraction and the neighboring ideas it depends on.
Mental model
Think of Request-Response as one piece of the larger computing map. It is easiest to understand when you ask two questions: what problem does it solve, and what assumptions does it make about the concepts below it?
Common mistakes
- Using Request-Response as a buzzword without understanding the problem it solves.
- Learning the definition in isolation instead of connecting it to nearby concepts.
Related concepts
- Requires: Packet
- Relates to: HTTP