Logo Questions Linux Laravel Mysql Ubuntu Git Menu
HTML CSS JAVASCRIPT SQL PYTHON PHP BOOTSTRAP JAVA JQUERY R React Kotlin
 

What is the difference between Socket and RPC?

Tags:

operating-system

sockets

rpc

ipc

What is the actual difference between Socket and RPC (Remote Procedure Call)?

As per my understanding both's working is based on Client–server model. Also which one should be used in which conditions?

PS: Confusion arise while reading Operating System Concepts by Galvin

like image 750
roottraveller Avatar asked Sep 09 '17 08:09

roottraveller

People also ask

What is the advantage of RPC over socket programming?

The major benefits of RPC are twofold: the programmer can now use procedure call semantics and writing distributed applications is simplified because RPC hides all of the network code into stub functions. Also, application programs don't have to worry about details (such as sockets, port numbers, byte ordering).

What is the difference between RPC and HTTP?

RPC is action-oriented. Supports HTTP methods GET, POST, PUT, PATCH, and DELETE. RPC only supports GET and POST requests.

What is a RPC system?

gRPC is a modern open source high performance Remote Procedure Call (RPC) framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication.

Is RPC TCP or UDP?

Generally, RPC applications will use UDP when sending data, and only fall back to TCP when the data to be transferred doesn't fit into a single UDP datagram. Of course, client programs have to have a way to find out which port a program number maps to.

1 Answers

Short answer:

RPC is the protocol. The socket provides access to the transport to implement that protocol.

RPC is the service and protocol offered by the operating system to allow code to be triggered for running by a remote application. It has a defined protocol by which procedures or objects can be accessed by another device over a network. An implementation of RPC can be done over basically any network transport (e.g. TCP, UDP, cups with strings).

The socket is just a programming abstraction such that the application can send and receive data with another device through a particular network transport. You implement protocols (such as RPC) on top of a transport (such as TCP) with a socket.

like image 86
selbie Avatar answered Oct 19 '22 13:10

selbie
Sign in to Comment

Related questions

Linux API to determine sockets owned by a process
Sending message to specific client in Socket IO
Non-blocking multiprocessing.connection.Listener?
TCP connection, bash only
What's the difference between BeginConnect and ConnectAsync?
Are there any module that works like django admin in Nodejs?
close() socket directly after send(): unsafe?
node.js - handling TCP socket error ECONNREFUSED
Best way to do interprocess communication on Mac OS X
"An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full"
Unix Sockets in Go
Receiving Broadcast Packets in Python
How to find a list of sockets held by a process in windows?
Debugging in XCode as root
how listening to a socket works
Adding support for IPv6 in IPv4 client/server apps - sin6_flowinfo and sin6_scope_id fields?
Converting a socket resource into a stream socket
Android connect to tethering socket
"java.net.BindException: Address already in use" when trying to do rapid Socket creation and destruction for load testing
Does closing the inputstream of a socket also close the socket connection?

Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!