<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>backend on Ritesh Sonawane</title><link>https://riteshsonawane.com/tags/backend/</link><description>Recent content in backend on Ritesh Sonawane</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 09 Feb 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://riteshsonawane.com/tags/backend/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview of gRPC</title><link>https://riteshsonawane.com/blog/overview-of-grpc/</link><pubDate>Sun, 09 Feb 2025 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/overview-of-grpc/</guid><description>&lt;p&gt;Taking HTTP/2 to next Level&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Before understanding gRPC lets see what is RPC&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="what-is-rpcremote-procedure-call"&gt;What is RPC(remote procedure call)?&lt;/h2&gt;
&lt;p&gt;RPC is a communication protocol which allows a program to execute functions on a remote server as if it was a local function. RPC simplifies distributed computing by hiding network complexity.&lt;/p&gt;
&lt;p&gt;Consider you have a program calling a function, but here this function execution is on a remote server. The program which is calling this function does needs to know anything about the network details.&lt;/p&gt;</description></item></channel></rss>