Show in graph
API

Product → API Products

RPC

A communication style where a program invokes a procedure on another process or machine as if it were local.

Motivation

RPC is useful because it gives engineers a precise handle on a recurring problem: a communication style where a program invokes a procedure on another process or machine as if it were local.. It helps you decide what to pay attention to, what abstractions are available, and which tradeoffs matter in real systems.

Where it fits

RPC 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 RPC 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 RPC as a buzzword without understanding the problem it solves.
  • Learning the definition in isolation instead of connecting it to nearby concepts.
  • Requires: TCP