<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kryo on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/kryo/</link>
    <description>Recent content in Kryo on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/kryo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Java Serialization Libraries Compared: Kryo vs Protocol Buffers vs Apache Avro vs Apache Thrift</title>
      <link>https://www.pistack.xyz/posts/2026-07-30-java-serialization-libraries-kryo-protobuf-avro-thrift/</link>
      <pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-30-java-serialization-libraries-kryo-protobuf-avro-thrift/</guid>
      <description>&lt;p&gt;Serialization — converting objects to bytes and back — is fundamental to distributed systems. Every microservice that communicates over a network, every message queue that persists events, and every cache that stores objects must serialize data. Java&amp;rsquo;s built-in &lt;code&gt;Serializable&lt;/code&gt; interface has been the default for decades, but it is slow, verbose, and a well-known security vulnerability vector. The ecosystem has produced several high-performance alternatives.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
