{"id":48535,"date":"2025-02-18T08:29:44","date_gmt":"2025-02-18T08:29:44","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=48535"},"modified":"2025-02-18T08:29:44","modified_gmt":"2025-02-18T08:29:44","slug":"a-complete-guide-of-rpc-remote-procedure-call","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/a-complete-guide-of-rpc-remote-procedure-call\/","title":{"rendered":"A Complete Guide of RPC (Remote Procedure Call)"},"content":{"rendered":"\n

What is RPC (Remote Procedure Call)?<\/h2>\n\n\n\n

\ud83d\udd39 What is RPC (Remote Procedure Call)?<\/strong><\/h2>\n\n\n\n

Remote Procedure Call (RPC)<\/strong> is a protocol<\/strong> that allows a computer program to execute a function or procedure on another computer (remote server) as if it were a local function<\/strong>.<\/p>\n\n\n\n

\u2705 Key Idea<\/strong>: RPC enables communication between different processes across a network or within the same system<\/strong>.
\u2705 Used In<\/strong>: Microservices, Distributed Systems, API Communication, Cloud Computing.<\/p>\n\n\n\n

\n\n\n\n

\ud83d\udd39 How Does RPC Work?<\/strong><\/h2>\n\n\n\n

1\ufe0f\u20e3 Client sends a request<\/strong> \u2192 Calls a function on a remote server.
2\ufe0f\u20e3 Server processes the request<\/strong> \u2192 Executes the function.
3\ufe0f\u20e3 Server sends a response<\/strong> \u2192 Returns the output to the client.<\/p>\n\n\n\n

\ud83d\udccc Example of RPC Flow<\/strong>:<\/p>\n\n\n

Client App  \u2500\u2500 Request (RPC Call) \u2500\u2500> Remote Server  \nRemote Server  \u2500\u2500 Process & Execute \u2500\u2500> Send Response  \nClient App  \u2500\u2500 Receive & Process Response \u2500\u2500> Done \u2705\n<\/code><\/span><\/pre>\n\n\n
\n\n\n\n
\ud83d\udd39 Types of RPC<\/strong><\/h2>\n\n\n\n
1\ufe0f\u20e3 Synchronous RPC<\/strong><\/h3>\n\n\n\n
    \n
  • Client waits<\/strong> for the server to respond before continuing.<\/li>\n\n\n\n
  • Example<\/strong>: Traditional API calls (like REST).<\/li>\n<\/ul>\n\n\n\n
    2\ufe0f\u20e3 Asynchronous RPC<\/strong><\/h3>\n\n\n\n
      \n
    • Client does not wait<\/strong> for a response, allowing parallel execution.<\/li>\n\n\n\n
    • Example<\/strong>: Event-driven microservices.<\/li>\n<\/ul>\n\n\n\n
      \n\n\n\n
      \ud83d\udd39 RPC vs. REST API<\/strong><\/h2>\n\n\n\n
      Feature<\/th>RPC<\/th>REST API<\/th><\/tr><\/thead>
      Protocol<\/strong><\/td>Can use HTTP, TCP, UDP, gRPC, etc.<\/strong><\/td>Uses HTTP<\/strong><\/td><\/tr>
      Data Format<\/strong><\/td>Binary (Protocol Buffers, Thrift, Avro)<\/strong> or Text (JSON, XML)<\/strong><\/td>JSON\/XML<\/strong><\/td><\/tr>
      Performance<\/strong><\/td>Faster (Binary format + Compression)<\/strong><\/td>Slower due to HTTP overhead<\/strong><\/td><\/tr>
      Streaming Support<\/strong><\/td>Yes (gRPC, Thrift, WebSockets)<\/strong><\/td>Limited (Needs WebSockets)<\/strong><\/td><\/tr>
      Use Case<\/strong><\/td>Microservices, High-Performance APIs<\/strong><\/td>Web & Mobile APIs<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n
      \ud83d\udd39 Popular RPC Frameworks<\/strong><\/h2>\n\n\n\n
      RPC Framework<\/strong><\/th>Used For<\/strong><\/th>Protocol<\/strong><\/th><\/tr><\/thead>
      gRPC<\/strong><\/td>Microservices, Cloud APIs<\/td>HTTP\/2 + Protocol Buffers<\/strong><\/td><\/tr>
      Apache Thrift<\/strong><\/td>High-speed RPCs<\/td>Binary Protocol, TCP<\/strong><\/td><\/tr>
      JSON-RPC<\/strong><\/td>Web APIs<\/td>HTTP + JSON<\/strong><\/td><\/tr>
      XML-RPC<\/strong><\/td>Legacy systems<\/td>HTTP + XML<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n
      \ud83d\udd39 Example of RPC Call<\/strong><\/h2>\n\n\n\n
      Using gRPC (Google RPC) in Python:<\/strong><\/p>\n\n\n
      import<\/span> grpc\nimport<\/span> example_pb2\nimport<\/span> example_pb2_grpc\n\nchannel = grpc.insecure_channel('localhost:50051'<\/span>)\nstub = example_pb2_grpc.GreeterStub(channel)\nresponse = stub.SayHello(example_pb2.HelloRequest(name='Alice'<\/span>))\nprint(response.message)\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      \u2705 This sends an RPC request<\/strong> to a server and gets a response.<\/p>\n\n\n\n
      \n\n\n\n
      \ud83c\udfaf When to Use RPC?<\/strong><\/h2>\n\n\n\n
      \u2705 When high-speed communication<\/strong> is needed (Microservices, Cloud).
      \u2705 When APIs must support streaming & multiplexing<\/strong> (gRPC).
      \u2705 When services need to communicate in different programming languages<\/strong>.<\/p>\n\n\n\n
      What is an RPC Framework?<\/h2>\n\n\n\n
      \ud83d\udd39 What is an RPC Framework?<\/strong><\/h2>\n\n\n\n
      An RPC (Remote Procedure Call) framework<\/strong> is a set of tools, libraries, and protocols<\/strong> that allow applications to execute functions or procedures on a remote server as if they were local functions<\/strong>.<\/p>\n\n\n\n
      \u2705 Purpose:<\/strong> Simplifies communication between distributed systems, microservices, and cloud applications.
      \u2705 Example Use Case:<\/strong> A frontend app calling a backend function on a remote server without worrying about networking details.<\/p>\n\n\n\n
      \n\n\n\n
      \ud83d\udd39 How Does an RPC Framework Work?<\/strong><\/h2>\n\n\n\n
      1\ufe0f\u20e3 Client makes an RPC request<\/strong> (calls a function remotely).
      2\ufe0f\u20e3 RPC framework serializes the request<\/strong> (converts data into a transportable format).
      3\ufe0f\u20e3 Server receives and processes the request<\/strong>.
      4\ufe0f\u20e3 RPC framework deserializes the response<\/strong> and returns it to the client.<\/p>\n\n\n\n
      \ud83d\udccc Example of an RPC Call Flow:<\/strong><\/p>\n\n\n
      Client  \u2500\u2500> RPC Framework \u2500\u2500> Network \u2500\u2500> Server  \nClient  <\u2500\u2500 RPC Framework <\u2500\u2500 Network <\u2500\u2500 Server Response\n<\/code><\/span><\/pre>\n\n\n
      \ud83d\udca1 Think of it like calling a function, but it runs on another server!<\/strong> \ud83d\ude80<\/p>\n\n\n\n
      \n\n\n\n
      \ud83d\udd39 Popular RPC Frameworks<\/strong><\/h2>\n\n\n\n
      RPC Framework<\/strong><\/th>Used For<\/strong><\/th>Protocol<\/strong><\/th>Serialization Format<\/strong><\/th><\/tr><\/thead>
      gRPC<\/strong><\/td>Microservices, Cloud APIs<\/td>HTTP\/2<\/td>Protocol Buffers (ProtoBuf)<\/td><\/tr>
      Apache Thrift<\/strong><\/td>Cross-language RPC<\/td>TCP, HTTP<\/td>Compact Binary Format<\/td><\/tr>
      JSON-RPC<\/strong><\/td>Web APIs, JavaScript-based Apps<\/td>HTTP, WebSockets<\/td>JSON<\/td><\/tr>
      XML-RPC<\/strong><\/td>Legacy Systems<\/td>HTTP<\/td>XML<\/td><\/tr>
      ZeroMQ (\u00d8MQ)<\/strong><\/td>High-performance messaging<\/td>Custom (No built-in protocol)<\/td>Custom<\/td><\/tr>
      Dapr<\/strong><\/td>Cloud-Native Applications<\/td>HTTP\/gRPC<\/td>JSON\/ProtoBuf<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n
      \ud83d\udd39 Why Use an RPC Framework?<\/strong><\/h2>\n\n\n\n
      \u2705 Simplicity<\/strong> \u2192 Developers call remote functions like local functions.
      \u2705 High Performance<\/strong> \u2192 Many frameworks (like gRPC) use binary serialization<\/strong> for fast data transmission.
      \u2705 Cross-Language Support<\/strong> \u2192 Works across different programming languages (e.g., Python client calling a Go server).
      \u2705 Streaming Support<\/strong> \u2192 Some frameworks (e.g., gRPC) support bidirectional streaming<\/strong>.<\/p>\n\n\n\n
      \n\n\n\n
      \ud83d\udd39 gRPC Example (Python)<\/strong><\/h2>\n\n\n\n
      Define an RPC Service (hello.proto<\/code>):<\/strong><\/p>\n\n\n
      syntax = \"proto3\"<\/span>;\n\nservice Greeter {\n  rpc SayHello (HelloRequest) returns (HelloReply);\n}\n\nmessage HelloRequest {\n  string name = 1<\/span>;\n}\n\nmessage HelloReply {\n  string message = 1<\/span>;\n}\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      \u2705 The RPC framework<\/strong> handles serialization, networking, and responses automatically!<\/p>\n\n\n\n
      \n\n\n\n
      \ud83c\udfaf Final Thoughts<\/strong><\/h2>\n\n\n\n
      \ud83d\udd25 An RPC framework helps build high-performance distributed systems efficiently!<\/strong> \ud83d\udd25
      \u2705 Best for:<\/strong> Microservices, Cloud APIs, and High-Speed Communication.
      \u2705 Best choice:<\/strong> gRPC for modern systems, Thrift for cross-language, and JSON-RPC for web apps.<\/strong><\/p>\n\n\n\n
      Difference Between RPC and RPC Framework<\/h2>\n\n\n\n
      Aspect<\/strong><\/th>RPC (Remote Procedure Call)<\/strong><\/th>RPC Framework<\/strong><\/th><\/tr><\/thead>
      Definition<\/strong><\/td>A concept<\/strong> that allows calling functions on a remote server as if they were local.<\/td>A set of tools, libraries, and protocols<\/strong> that implement RPC functionality.<\/td><\/tr>
      Functionality<\/strong><\/td>Enables communication between client and server in distributed systems.<\/td>Provides ready-to-use implementations<\/strong> for handling RPC calls, serialization, security, and networking.<\/td><\/tr>
      Example Concept<\/strong><\/td>A client requests a function (getUserDetails()<\/code>) on a remote server.<\/td>A framework like gRPC, Apache Thrift, or JSON-RPC<\/strong> handles the networking, serialization, and execution of getUserDetails()<\/code>.<\/td><\/tr>
      Transport Mechanism<\/strong><\/td>Can work over HTTP, TCP, UDP, WebSockets, etc.<\/strong><\/td>Uses specific transport mechanisms like HTTP\/2 (gRPC)<\/strong>, TCP (Thrift)<\/strong>, or HTTP (JSON-RPC)<\/strong>.<\/td><\/tr>
      Serialization<\/strong><\/td>Requires a way to encode and decode data (e.g., JSON, XML, Binary).<\/td>Built-in serialization formats<\/strong> like ProtoBuf (gRPC)<\/strong>, JSON (JSON-RPC)<\/strong>, or Binary (Thrift)<\/strong>.<\/td><\/tr>
      Security<\/strong><\/td>Must be implemented separately (e.g., authentication, encryption).<\/td>Many frameworks provide built-in TLS encryption, authentication, and access control<\/strong>.<\/td><\/tr>
      Cross-Language Support<\/strong><\/td>Requires manual implementation for different languages.<\/td>Provides auto-generated client and server code<\/strong> for multiple languages (e.g., Python, Java, Go, C++).<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      How RPC Works (Conceptually)?<\/h2>\n\n\n\n
      1\ufe0f\u20e3 Client Calls a Function<\/strong><\/p>\n\n\n\n
        \n
      • A client program calls a function (getUserDetails()<\/code>) that is actually located on a remote server.<\/li>\n<\/ul>\n\n\n\n
        2\ufe0f\u20e3 Request Serialization<\/strong><\/p>\n\n\n\n
          \n
        • The function call’s parameters (data) are converted into a format<\/strong> that can be transmitted over a network (e.g., JSON, Protocol Buffers, XML, Binary).<\/li>\n<\/ul>\n\n\n\n
          3\ufe0f\u20e3 Network Transmission<\/strong><\/p>\n\n\n\n
            \n
          • The serialized data is sent over a network<\/strong> (via HTTP, TCP, UDP, WebSockets, etc.).<\/li>\n<\/ul>\n\n\n\n
            4\ufe0f\u20e3 Server Receives the Request<\/strong><\/p>\n\n\n\n
              \n
            • The server’s RPC system<\/strong> deserializes<\/strong> the request and calls the actual function<\/strong> on the server.<\/li>\n<\/ul>\n\n\n\n
              5\ufe0f\u20e3 Function Execution & Response<\/strong><\/p>\n\n\n\n
                \n
              • The server executes the function<\/strong> (getUserDetails()<\/code>) and sends the response back<\/strong> to the client.<\/li>\n<\/ul>\n\n\n\n
                6\ufe0f\u20e3 Client Receives the Response<\/strong><\/p>\n\n\n\n
                  \n
                • The client deserializes<\/strong> the response and continues execution as if the function ran locally.<\/li>\n<\/ul>\n\n\n\n
                  \ud83d\udccc RPC Conceptual Flow:<\/strong><\/p>\n\n\n\n
                  pgsqlCopyEditClient \u2500\u2500\u2500> (Serialize Data) \u2500\u2500\u2500> Network \u2500\u2500\u2500> Server  \nServer \u2500\u2500\u2500> (Execute Function) \u2500\u2500\u2500> Return Response \u2500\u2500\u2500> Client  \n<\/code><\/pre>\n\n\n\n
                  \ud83d\udd39 RPC vs. Normal Function Calls<\/strong><\/h2>\n\n\n\n
                  Feature<\/th>Local Function Call<\/th>Remote Procedure Call (RPC)<\/th><\/tr><\/thead>
                  Execution Location<\/strong><\/td>Runs on the same machine<\/strong><\/td>Runs on a remote server<\/strong><\/td><\/tr>
                  Data Passing<\/strong><\/td>Direct memory access<\/td>Data is serialized and sent over the network<\/strong><\/td><\/tr>
                  Performance<\/strong><\/td>Fast (no network delay)<\/td>Slower (network latency)<\/td><\/tr>
                  Complexity<\/strong><\/td>Simple<\/td>Requires handling network failures, serialization, security<\/strong><\/td><\/tr>
                  Use Case<\/strong><\/td>Local programs<\/td>Microservices, Cloud APIs, Distributed Systems<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  \n\n\n\n
                  \ud83d\udd39 Real-World Use Cases of RPC<\/strong><\/h2>\n\n\n\n
                  \u2705 Microservices Communication<\/strong> \u2192 Services talk to each other in cloud-native applications.
                  \u2705 Database Requests<\/strong> \u2192 Clients call database functions remotely.
                  \u2705 Remote System Administration<\/strong> \u2192 Commands are executed on remote servers.
                  \u2705 Game Servers & Multiplayer Apps<\/strong> \u2192 Actions from one player affect other players over a network.<\/p>\n\n\n\n
                  \ud83d\udd39 List of All Popular RPC Frameworks<\/strong><\/h2>\n\n\n\n
                  RPC frameworks simplify remote function execution<\/strong> by handling networking, serialization, and security. Below is a list of widely used RPC frameworks<\/strong> categorized based on their use cases.<\/p>\n\n\n\n
                  \n\n\n\n
                  1\ufe0f\u20e3 Modern High-Performance RPC Frameworks<\/strong><\/h2>\n\n\n\n
                  Framework<\/strong><\/th>Description<\/strong><\/th>Protocol<\/strong><\/th>Serialization Format<\/strong><\/th>Best For<\/strong><\/th><\/tr><\/thead>
                  gRPC<\/strong><\/td>Google\u2019s high-performance RPC framework<\/td>HTTP\/2<\/strong><\/td>Protocol Buffers (ProtoBuf)<\/strong><\/td>Microservices, Cloud APIs<\/td><\/tr>
                  Apache Thrift<\/strong><\/td>Cross-language RPC system<\/td>TCP, HTTP<\/strong><\/td>Compact Binary, JSON, Simple JSON<\/strong><\/td>Large-scale distributed systems<\/td><\/tr>
                  Cap\u2019n Proto<\/strong><\/td>High-speed serialization and RPC<\/td>Custom (No extra encoding needed)<\/strong><\/td>Cap\u2019n Proto (Zero Parsing Overhead)<\/strong><\/td>Low-latency systems<\/td><\/tr>
                  Dapr<\/strong><\/td>Cloud-native distributed application runtime<\/td>HTTP, gRPC<\/strong><\/td>JSON, ProtoBuf<\/strong><\/td>Microservices & Kubernetes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  \n\n\n\n
                  2\ufe0f\u20e3 Web-Based RPC Frameworks<\/strong><\/h2>\n\n\n\n
                  Framework<\/strong><\/th>Description<\/strong><\/th>Protocol<\/strong><\/th>Serialization Format<\/strong><\/th>Best For<\/strong><\/th><\/tr><\/thead>
                  JSON-RPC<\/strong><\/td>Lightweight RPC using JSON over HTTP\/WebSockets<\/td>HTTP, WebSockets<\/strong><\/td>JSON<\/strong><\/td>Web applications, JavaScript-based systems<\/td><\/tr>
                  XML-RPC<\/strong><\/td>Simple RPC protocol using XML over HTTP<\/td>HTTP<\/strong><\/td>XML<\/strong><\/td>Legacy systems<\/td><\/tr>
                  WAMP (Web Application Messaging Protocol)<\/strong><\/td>Web-based RPC with real-time pub\/sub<\/td>WebSockets, TCP<\/strong><\/td>JSON, MsgPack, CBOR<\/strong><\/td>WebSockets-based APIs<\/td><\/tr>
                  Falcor<\/strong><\/td>Netflix\u2019s RPC for efficient data fetching<\/td>HTTP<\/strong><\/td>JSON<\/strong><\/td>Web applications<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  \n\n\n\n
                  3\ufe0f\u20e3 Messaging-Based RPC Frameworks<\/strong><\/h2>\n\n\n\n
                  Framework<\/strong><\/th>Description<\/strong><\/th>Protocol<\/strong><\/th>Serialization Format<\/strong><\/th>Best For<\/strong><\/th><\/tr><\/thead>
                  ZeroMQ (\u00d8MQ)<\/strong><\/td>High-performance messaging library<\/td>TCP, IPC, Multicast<\/strong><\/td>Custom<\/strong><\/td>Low-latency, real-time systems<\/td><\/tr>
                  Apache Avro<\/strong><\/td>Schema-based RPC with a focus on Big Data<\/td>TCP, HTTP<\/strong><\/td>Avro Binary, JSON<\/strong><\/td>Big Data, Streaming (Kafka, Hadoop)<\/td><\/tr>
                  MessagePack-RPC<\/strong><\/td>Lightweight binary-based RPC<\/td>TCP, UDP<\/strong><\/td>MessagePack<\/strong><\/td>IoT & high-performance applications<\/td><\/tr>
                  Nanomsg<\/strong><\/td>Simplified version of ZeroMQ<\/td>TCP, IPC<\/strong><\/td>Custom<\/strong><\/td>High-speed messaging<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  \n\n\n\n
                  4\ufe0f\u20e3 Enterprise & Legacy RPC Frameworks<\/strong><\/h2>\n\n\n\n
                  Framework<\/strong><\/th>Description<\/strong><\/th>Protocol<\/strong><\/th>Serialization Format<\/strong><\/th>Best For<\/strong><\/th><\/tr><\/thead>
                  CORBA (Common Object Request Broker Architecture)<\/strong><\/td>Classic RPC framework for enterprise systems<\/td>IIOP (TCP-based)<\/strong><\/td>Binary (IDL-based)<\/strong><\/td>Legacy enterprise applications<\/td><\/tr>
                  RMI (Remote Method Invocation)<\/strong><\/td>Java\u2019s built-in RPC mechanism<\/td>JRMP (Java Remote Method Protocol)<\/strong><\/td>Java Serialization<\/strong><\/td>Java-based distributed applications<\/td><\/tr>
                  Hessian<\/strong><\/td>Lightweight binary-based RPC<\/td>HTTP<\/strong><\/td>Hessian Binary Format<\/strong><\/td>Java & cross-platform systems<\/td><\/tr>
                  TARS<\/strong><\/td>Tencent\u2019s distributed RPC framework<\/td>TCP, HTTP<\/strong><\/td>TARS, ProtoBuf, JSON<\/strong><\/td>Large-scale microservices<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  \n\n\n\n
                  5\ufe0f\u20e3 Blockchain & Decentralized RPC Frameworks<\/strong><\/h2>\n\n\n\n
                  Framework<\/strong><\/th>Description<\/strong><\/th>Protocol<\/strong><\/th>Serialization Format<\/strong><\/th>Best For<\/strong><\/th><\/tr><\/thead>
                  Ethereum JSON-RPC<\/strong><\/td>RPC API for Ethereum blockchain<\/td>HTTP, WebSockets<\/strong><\/td>JSON<\/strong><\/td>Blockchain applications<\/td><\/tr>
                  Bitcoin RPC<\/strong><\/td>RPC interface for Bitcoin nodes<\/td>HTTP<\/strong><\/td>JSON<\/strong><\/td>Cryptocurrency development<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  \n\n\n\n
                  \ud83d\udd39 Choosing the Right RPC Framework<\/strong><\/h2>\n\n\n\n
                  Use Case<\/strong><\/th>Recommended Framework<\/strong><\/th><\/tr><\/thead>
                  Microservices & Cloud<\/strong><\/td>gRPC, Thrift, Dapr<\/td><\/tr>
                  Web-Based RPC<\/strong><\/td>JSON-RPC, WAMP, Falcor<\/td><\/tr>
                  Big Data & Streaming<\/strong><\/td>Apache Avro, MessagePack-RPC<\/td><\/tr>
                  Low-Latency & High-Performance<\/strong><\/td>ZeroMQ, Cap\u2019n Proto<\/td><\/tr>
                  Enterprise & Legacy Apps<\/strong><\/td>CORBA, RMI, Hessian<\/td><\/tr>
                  Blockchain Apps<\/strong><\/td>Ethereum JSON-RPC, Bitcoin RPC<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  \n\n\n\n
                  \ud83c\udfaf Final Thoughts<\/strong><\/h2>\n\n\n\n
                  \u2705 If you need a high-performance modern RPC framework<\/strong>, use gRPC or Apache Thrift<\/strong>.
                  \u2705 For web-based applications<\/strong>, JSON-RPC<\/strong> is a lightweight option.
                  \u2705 For low-latency, high-speed messaging<\/strong>, ZeroMQ<\/strong> or Cap\u2019n Proto<\/strong> are great choices.
                  \u2705 For distributed systems and big data<\/strong>, Apache Avro<\/strong> is recommended.<\/p>\n\n\n\n
                  \ud83d\udd39 Default RPC Methods in Different Scenarios<\/strong><\/h2>\n\n\n\n
                  Below is a breakdown of what happens by default<\/strong> when you call a remote function in different environments.<\/p>\n\n\n\n
                  Scenario<\/strong><\/th>What Happens By Default?<\/strong><\/th>Default RPC Framework<\/strong><\/th><\/tr><\/thead>
                  PHP in XAMPP (Apache Server)<\/strong><\/td>No native RPC; you must use JSON-RPC, SOAP, or REST<\/td>\u274c None (you must specify)<\/td><\/tr>
                  Java Calling Remote Functions<\/strong><\/td>Uses Java RMI (Remote Method Invocation)<\/td>\u2705 Java RMI<\/strong><\/td><\/tr>
                  Python Calling a Remote Function<\/strong><\/td>Uses built-in xmlrpc.client<\/code> for XML-RPC<\/td>\u2705 XML-RPC<\/strong><\/td><\/tr>
                  Node.js Communicating with Remote Services<\/strong><\/td>Typically uses HTTP API calls (REST)<\/td>\u2705 HTTP (REST)<\/strong><\/td><\/tr>
                  .NET \/ C# Calling Remote Services<\/strong><\/td>Uses WCF (Windows Communication Foundation)<\/td>\u2705 WCF (SOAP\/XML-RPC)<\/strong><\/td><\/tr>
                  C++ Distributed Systems<\/strong><\/td>Uses CORBA (Common Object Request Broker Architecture)<\/td>\u2705 CORBA<\/strong><\/td><\/tr>
                  Web Browsers Calling Remote Functions<\/strong><\/td>Uses AJAX (JavaScript HTTP Requests)<\/td>\u2705 REST over HTTP (AJAX, Fetch API)<\/strong><\/td><\/tr>
                  Linux System Calls<\/strong><\/td>Uses gRPC<\/code> or DBus<\/code> for inter-process communication<\/td>\u2705 gRPC, DBus<\/strong><\/td><\/tr>
                  Blockchain Smart Contracts (Ethereum, Bitcoin, etc.)<\/strong><\/td>Uses JSON-RPC to communicate with nodes<\/td>\u2705 JSON-RPC<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"
                  What is RPC (Remote Procedure Call)? \ud83d\udd39 What is RPC (Remote Procedure Call)? Remote Procedure Call (RPC) is a protocol that allows a computer program to execute a function or… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-48535","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48535","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=48535"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48535\/revisions"}],"predecessor-version":[{"id":48536,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/48535\/revisions\/48536"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=48535"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=48535"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=48535"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}