<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cassandra on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/cassandra/</link><description>Recent content in Cassandra 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/cassandra/rss.xml" rel="self" type="application/rss+xml"/><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>