<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Grpc on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/grpc/</link>
    <description>Recent content in Grpc on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/grpc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>gRPC Gateway vs Connect vs gRPC-Web: Bridge gRPC Services to REST &amp; Web Clients 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-24-grpc-gateway-vs-connect-vs-grpc-web-self-hosted-rest-proxy-guide-2026/</link>
      <pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-24-grpc-gateway-vs-connect-vs-grpc-web-self-hosted-rest-proxy-guide-2026/</guid>
      <description>&lt;p&gt;If you are running gRPC services internally, you have already discovered the performance and type-safety benefits of Protocol Buffers. But external clients — web browsers, mobile apps, third-party integrations — cannot speak gRPC directly. Browsers have no native gRPC support, and many external partners expect standard REST/JSON APIs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
