<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gossip on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/gossip/</link><description>Recent content in Gossip on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Tue, 07 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.mickeyzzc.tech/en/tags/gossip/rss.xml" rel="self" type="application/rss+xml"/><item><title>Gossip Protocol Core Principles</title><link>https://blog.mickeyzzc.tech/en/posts/network/gossip-protocol-theory/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/network/gossip-protocol-theory/</guid><description>&lt;p&gt;In P2P networks, every node needs to learn the global cluster state—which peers are online, where data is stored, and whether new nodes have joined or old ones left—without relying on any central server. The essence of this problem is: &lt;strong&gt;how can information be disseminated efficiently and reliably across an unpredictable, dynamic network?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Gossip protocol (also called Epidemic protocol) offers an elegant answer: mimic the spread pattern of infectious diseases. Each node randomly selects several neighbors and exchanges the information it knows. The message spreads like a virus, eventually reaching all nodes with high probability. It requires no centralized coordinator and has natural tolerance for network partitions and node failures.&lt;/p&gt;</description></item><item><title>SWIM Protocol and Cluster Membership Management</title><link>https://blog.mickeyzzc.tech/en/posts/network/swim-membership-protocol/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/network/swim-membership-protocol/</guid><description>&lt;p&gt;In the previous article, we explored the core principles of the Gossip protocol in depth—Epidemic propagation models, the distinction between Anti-Entropy and Rumor-Mongering, and the mathematical foundation of the Phi Accrual failure detector. Gossip provides a general mechanism for information dissemination, but to build a complete distributed cluster, information dissemination alone is not enough: &lt;strong&gt;every node needs to know who else is in the cluster—who is online, who has left, and who has just joined.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Gossip in Production Systems</title><link>https://blog.mickeyzzc.tech/en/posts/network/gossip-production-systems/</link><pubDate>Tue, 07 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/network/gossip-production-systems/</guid><description>&lt;p&gt;The previous four articles in this series built a complete knowledge foundation—from Epidemic propagation theory in Gossip, to the SWIM membership protocol, to P2P implementations in Rust and Go, and finally to production best practices. Now it is time to apply this knowledge to real distributed systems.&lt;/p&gt;
&lt;p&gt;This article examines six representative systems and how they adapt Gossip protocols to different scenarios: from Gossipsub parameter tuning to Raft membership changes, from Redis Cluster PING/PONG to Cassandra&amp;rsquo;s GossipDigest protocol, and the hidden Gossip routing mechanisms inside message queues.&lt;/p&gt;</description></item></channel></rss>