Implementing the three messages of Gossip round

Image for post
Image for post

In the first part of the blog series, I covered the various code constructs used to facilitate transfer of knowledge as gossip messages in Cassandra. The content covered in the first part was generic to some extent in the sense that it could be applied to any distributed system, whereas this article will cover concepts specific to Cassandra, (obviously) by extending the understanding built in the previous blog. So, please I highly recommend to read the first part once before you dive further.

Let’s start with the below image taken, which was also used in the first blog. As mentioned there, gossip in Cassandra is very similar to the TCP three-way handshake. …

Lets learn while gossiping !😛

Image for post
Image for post

Well, after chilling around for a week in my notice period, I decided to do something useful and started reading a few blogs. Throughout the past 2 years of my career as a software developer , I have heard “office gossips” on how great Cassandra is. (pun absolutely intended)

Cassandra is one of the most popular NoSql distributed databases currently and after skimming through some usual online tutorials, I decided to learn more by diving into the source code itself. The code base is huge and so I had to pick a topic to dig deeper, Gossip protocol was my choice, primarily because it is not just specific to Cassandra but is an important tool for Failure Detection, Monitoring, Messaging And Other Good Things in a distributed setup in general.(ref)

Swarnim Singhal

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store