Interview Question: Understanding RPC Frameworks and Their Differences from SOA, SOAP, and REST

Interview Question 1: Explain Your Understanding of RPC Frameworks

RPC (Remote Procedure Call) is a common communication method in distributed systems that allows a program to invoke a procedure on another machine without the programmer handling the low‑level details.

Besides RPC, other data‑exchange mechanisms include distributed message queues, HTTP calls, databases, and distributed caches.

Both RPC and direct HTTP calls are end‑to‑end interactions without middleware.

In Simple Terms

RPC enables a client machine to call a function or method on a server machine and receive a result.

RPC hides the underlying communication details, so developers do not need to manage sockets or HTTP directly.

The client sends a request and the server returns a response, making remote calls feel like local function calls.

Follow‑up 1: How Is an RPC Framework Implemented?

An RPC framework typically involves three roles: provider, consumer, and registry.

Provider: the service that exposes functionality.

Consumer: the client that invokes the remote service.

Registry: the service‑registration and discovery component.

The overall process includes establishing communication, service addressing, network transmission (serialization/deserialization), and service invocation.

1. Establish Communication – Usually a TCP connection is created between client and server, either per request or as a long‑lived connection.

2. Service Addressing – The client must know the server’s host/IP, port, and method signature; registries such as Redis or Zookeeper often provide discovery.

3. Network Transmission

Serialization – Convert method name and parameters into binary data for transport.

Deserialization – Convert received binary data back into objects before invoking the local method (often via dynamic proxies like JDK proxy, CGLIB, or Javassist).

4. Service Invocation – The server executes the method, serializes the return value, sends it back, and the client deserializes it for further processing.

Interview Question 2: Compare RPC with SOA, SOAP, and REST

REST – An HTTP‑based style that typically uses JSON, is simple to learn, efficient, but offers lower security.

SOAP – A heavyweight XML‑based protocol with extensive standards (WS‑Security) for security, offering cross‑language and cross‑platform flexibility.

SOA – Service‑Oriented Architecture focuses on loosely coupled, coarse‑grained services that can be composed and deployed across a network, providing a higher‑level abstraction than simple B/S or Web‑Service models.