https://github.com/dhyanio/rpc-server-client

RPC: server & client
https://github.com/dhyanio/rpc-server-client

Last synced: 20 days ago
JSON representation

RPC: server & client

• Host: GitHub
• URL: https://github.com/dhyanio/rpc-server-client
• Owner: dhyanio
• License: mit
• Created: 2021-05-13T15:43:59.000Z (over 3 years ago)
• Default Branch: master
• Last Pushed: 2021-05-13T16:13:05.000Z (over 3 years ago)
• Last Synced: 2024-06-19T19:30:56.675Z (6 months ago)
• Language: Go
• Size: 6.84 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# What is RPC?

RPC is an inter-process communication that exchanges information between various

distributed systems. A computer called Alice can call functions (procedures) in another

computer called Bob in protocol format and can get the computed result back. Without

implementing the functionality locally, we can request things from a network that lies in

another place or geographical region.

### The entire process can be broken down into the following steps:

- Clients prepare function name and arguments to send

- Clients send them to an RPC server by dialing the connection

- The server receives the function name and arguments

- The server executes the remote process

- The message will be sent back to the client

- The client collects the data from the request and uses it appropriately

Did you see the magic? The client is running as an independent program from the server.

Here, both the programs can be on different machines, and computing can still be shared.

This is the core concept of distributed systems. The tasks are divided and given to various

RPC servers. Finally, the client collects the results and uses them to take further decisions.

Custom RPC code is only useful when the client and server are both written in Go. So, in

order to have the RPC server consumed by multiple services, we need to define the JSON-

RPC over HTTP. Then, any other programming language can send a JSON string and get

JSON as the result back.

## JSON-RPC using Gorilla RPC

We saw that the Gorilla toolkit helps us by providing many useful libraries. It has libraries

such as Mux for routing, Handlers for middleware, and now, the gorilla/rpc library.

Using this, we can create RPC servers and clients that talk using JSON instead of a custom

reply pointer. Let's convert the preceding example into a much more useful one.

Consider this scenario. We have a JSON file on the server that has details of books (name,

ID, author). The client requests book information by making an HTTP request. When the

RPC server receives the request, it reads the file from the filesystem and parses it. If the

given ID matches any book, then the server sends the information back to the client in

JSON format. Let's look at the steps here: