<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>protobuf on GoScrapy Blog</title><link>http://goscrapy.com.ar/tags/protobuf/</link><description>Recent content in protobuf on GoScrapy Blog</description><generator>Hugo -- gohugo.io</generator><managingEditor>jackgris2@gmail.com (Gabriel Pozo)</managingEditor><webMaster>jackgris2@gmail.com (Gabriel Pozo)</webMaster><lastBuildDate>Sun, 16 Apr 2023 20:39:08 -0300</lastBuildDate><atom:link href="http://goscrapy.com.ar/tags/protobuf/index.xml" rel="self" type="application/rss+xml"/><item><title>Basics about a gRPC Server</title><link>http://goscrapy.com.ar/post/basics-about-a-grpc-server/</link><pubDate>Sun, 16 Apr 2023 20:39:08 -0300</pubDate><author>jackgris2@gmail.com (Gabriel Pozo)</author><guid>http://goscrapy.com.ar/post/basics-about-a-grpc-server/</guid><description>What&amp;rsquo;s gRPC? gRPC is a Remote Procedure Call (RPC) framework. RPC is an action-based paradigm, similar to remotely calling a function from another microservice. This makes gRPC a type of inter-process communication (IPC) protocol built around Protobufs to handle messaging between the client and the server. gRPC is perfect for intensive and efficient communication, because it supports client and server streaming.
Difference with REST? In contrast, REST is a resource-based protocol, which means the client tells the server what resource needs to be created, read, updated, or deleted based on the body of the request.</description></item></channel></rss>