<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Avro on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/avro/</link>
    <description>Recent content in Avro on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 03 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/avro/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go Serialization Libraries: encoding/gob vs msgp vs Protobuf vs Avro vs JSON</title>
      <link>https://www.pistack.xyz/posts/2026-07-03-go-serialization-libraries-gob-msgp-protobuf-avro-json/</link>
      <pubDate>Fri, 03 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-03-go-serialization-libraries-gob-msgp-protobuf-avro-json/</guid>
      <description>&lt;p&gt;Serialization is at the heart of every networked Go application. Whether you&amp;rsquo;re building gRPC microservices, persisting application state, or passing messages between goroutines, your choice of encoding format directly impacts throughput, latency, and schema evolution. Go&amp;rsquo;s standard library provides &lt;code&gt;encoding/json&lt;/code&gt;, &lt;code&gt;encoding/gob&lt;/code&gt;, and &lt;code&gt;encoding/xml&lt;/code&gt;, but a rich ecosystem of third-party libraries offers dramatically better performance and richer type support.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
