<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Service-Communication on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/service-communication/</link>
    <description>Recent content in Service-Communication on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 20 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/service-communication/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Open Source RPC Frameworks: gRPC vs Twirp vs Connect RPC vs Apache Dubbo Compared</title>
      <link>https://www.pistack.xyz/posts/2026-06-20-rpc-frameworks-grpc-twirp-connect-dubbo/</link>
      <pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-20-rpc-frameworks-grpc-twirp-connect-dubbo/</guid>
      <description>&lt;p&gt;Modern distributed systems depend on efficient service-to-service communication. While REST dominates public APIs, Remote Procedure Call (RPC) frameworks offer protocol buffers, binary serialization, streaming, and lower latency for internal microservice communication. This guide compares four leading open source RPC frameworks — &lt;strong&gt;gRPC&lt;/strong&gt;, &lt;strong&gt;Twirp&lt;/strong&gt;, &lt;strong&gt;Connect RPC&lt;/strong&gt;, and &lt;strong&gt;Apache Dubbo&lt;/strong&gt; — across features, performance, ecosystem, and self-hosting considerations.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
