What is the difference between RPC and RMI?

Question

Currently reading about RPC and RMI, I'm a bit confused about the difference.

When implementing RMI and for example gRPC, the syntax is basically the same.

They both have interfaces determining methods parameters and response.

They can both send objects in parameters (Java RMI doing it natively, C# gRPC with proto).

They both execute the request to the server through a method call on some object (based on the interface.

So what is the difference? Is it how the processes of data transfer happen between client and server?

By the looks of it RMI is just a Java implementation of RPC and gRPC is the C# implementation.

question from:https://stackoverflow.com/questions/65646238/what-is-the-difference-between-rpc-and-rmi

Answer 1

RPC stands for Remote Procedure Call which supports procedural programming. Tt’s almost like IPC mechanism wherever the software permits the processes to manage shared information Associated with an environment wherever completely different processes area unit death penalty on separate systems and essentially need message-based communication.

The above diagram shows the working steps in PRC implementation.

RMI stands for Remote Method Invocation, is a similar to PRC but it supports object-oriented programming which is the java’s feature. A thread is allowable to decision the strategy on a foreign object. In RMI, objects are passed as a parameter rather than ordinary data.

This diagram shows the client-server architecture of the RMI protocol.

RPC and RMI both are similar but the basic difference between RPC and RMI is that RPC supports procedural programming, on the other hand, RMI supports object-oriented programming.

Let’s see that the difference between RPC and RMI: