<?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 Pi Stack</title>
    <link>https://www.pistack.xyz/tags/protobuf/</link>
    <description>Recent content in Protobuf on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/protobuf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Protobuf Tooling: buf vs protolock vs protovalidate 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-07-self-hosted-protobuf-tools-buf-protolock-protovalidate-guide/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-07-self-hosted-protobuf-tools-buf-protolock-protovalidate-guide/</guid>
      <description>&lt;p&gt;Protocol Buffers (protobuf) have become the standard for defining APIs and serializing structured data in microservices architectures. But managing &lt;code&gt;.proto&lt;/code&gt; files across teams and repositories introduces challenges: schema drift, breaking changes, inconsistent code generation, and missing validation rules.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
