<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gossip-Protocol on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/gossip-protocol/</link>
    <description>Recent content in Gossip-Protocol on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/gossip-protocol/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Cluster Membership Protocols: memberlist vs serf vs SWIM Gossip Implementations</title>
      <link>https://www.pistack.xyz/posts/2026-06-19-self-hosted-cluster-membership-memberlist-serf-swim/</link>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-19-self-hosted-cluster-membership-memberlist-serf-swim/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Every self-hosted distributed system needs to answer a fundamental question: &amp;ldquo;Which nodes are alive right now?&amp;rdquo; This is the cluster membership problem — maintaining a consistent, eventually-accurate view of which servers are healthy and reachable. Getting this wrong leads to split-brain scenarios, missed failures, or unnecessary rebalancing cascades that degrade cluster stability.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
