How programmers make remote computers behave like they are sitting right next door
In short: Remote procedure calls allow software to trigger actions on distant machines as if they were local subroutines. By masking the complexity of network communication, this technique enables seamless interaction between distributed systems, though it introduces unique challenges regarding reliability and speed that developers must navigate to ensure robust performance.
At its core, a remote procedure call (RPC) is a mechanism for inter-process communication that lets a program execute code in a different address space. Whether that space exists on the same machine or across a network, the goal is location transparency: the programmer writes the same code regardless of where the procedure runs. This abstraction relies on a request-response model where the client initiates a call, waits for the server to process it, and receives a result.
The process involves several hidden steps. When a client calls a local stub, the stub performs marshalling—packing parameters into a message for transport. The operating system then transmits this data to the server, where a corresponding stub unmarshals the message and executes the actual procedure. The reply follows this same path in reverse. To standardize this across different platforms, developers often use an interface description language (IDL) to generate the necessary code for these interactions.
While the concept dates back to theoretical proposals in the 1970s, practical implementations emerged in the early 1980s, with Bruce Jay Nelson credited for coining the term in 1981. Early milestones included the Newcastle Connection in 1982 and Xerox’s Courier protocol. Over the decades, the model evolved through various iterations, such as the object-oriented remote method invocation (RMI) popular in the 1990s, and modern frameworks like gRPC that leverage binary serialization and HTTP/2.
Despite its utility, RPC is not a perfect substitute for local calls. Remote operations are inherently slower and less reliable due to unpredictable network conditions. If a call fails, the client may not know if the procedure was ever invoked, necessitating careful handling of idempotent procedures. Consequently, developers often confine RPC logic to specialized, low-level subsystems to manage these risks effectively.
Opens the Intellect+ feed with this card first. Swipe up for the next one.
Sources
- Summary by Intellect · source: Remote procedure call
To cite this card, link to https://intellectplus.co.uk/app/technology-remote-procedure-call.
How we source, check and correct cards: Editorial standards.
General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.
Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?
Related
More in UK & Ireland: inventions · More in Technology · Latest · A–Z · All topics