Thread by @Rapid_API

A complete introduction to RPC and gRPC

Microservices are usually written in different languages, making it challenging to manage them and exchange information.

Here gRPC comes into play.

Thread 🧵👇🏻

Before jumping onto gRPC, we need to understand what RPC is 👇🏻

📌 RPC

RPC stands for Remote Procedure Call, and it's a client-server communication method in use today.

In typical HTTP, the client makes a request and gets a response from the server.

RPC uses a function call. It means that on the client-side, you invoke a function that is written on the server-side code.

It only looks like you are calling it like a regular function but instead, it is happening through the network.

📌 gRPC

gRPC is an open-source framework developed by Google in 2015 for implementing RPC APIs using the HTTP/2 protocol.

The fun fact is that 'g' here does not stand for Google.

'g' stands for something different every gRPC release:

github.com/grpc/grpc/blob…

With gRPC, the abstraction has become easy since it is a function call. It also supports a lot of programming languages.

So you can use gRPC in microservices to communicate with other services that are written in some different programming language.

There are several benefits of using gRPC:

- Messages in gRPC are lightweight
- gRPC provides high performance
- 8 times faster than REST
- gRPC automatically generates code for different programming languages for the purpose of working with them

With that being said, this is the end of this thread.

We hope you find it useful. If so, follow @Rapid_API for more quality content. 💙