Answers: <p>Serf is gossip protocol implementation and has absolutely nothing to do with orchestration tools like k8s. Even if such protocol is used internally, then in most cases it isn't available for you applications running in given orchestrator.</p>
  
  <p>So if your app or workflow depends on gossip protocol, then you will have use out of Serf, otherwise there is no point.</p>
  
  <hr>
  
  <p><a href="https://en.wikipedia.org/wiki/Gossip_protocol" rel="nofollow noreferrer">Gossip protocol</a> is way of messaging to all nodes without:</p>
  
  <ul>
  <li>Centralized point of knowledge</li>
  <li>Single point of failure</li>
  <li>Using whole network capability of any of the nodes</li>
  </ul>
  
  <p>In simple words it works like "message chains" ("If you do not send this to N people you will never find your love" or something like that).</p>
  
  <ol>
  <li>One node send notification to N out of M of its fellows</li>
  <li>If you receive message that you have already received, then do nothing.</li>
  <li>Otherwise go to step 1.</li>
  </ol>
  
  <p>Given such simple protocol you can calculate probability when all your nodes will receive message with 99% chance.</p>
  
Answers: CC BY-SA 3.0
Answers: 2017-08-15T09:41:09.353Z
Answers: 2017-08-15T09:41:09.353Z
Answers: Hauleth
Body: <p>When the Hashicorp's website was checked it seems that there is another tool, i.e. Serf. Back in the day there was another tool called <code>otto</code>, but that was deprecated at a certain moment.</p>
  
  <p>After reading the <a href="https://www.serf.io/intro/use-cases.html" rel="nofollow noreferrer">use cases</a> I wonder whether it is an added value to use <code>serf</code> when a container orchestration platform like kubernetes is used.</p>
  
Tags: <monitoring>
Title: Is Serf an added value when a container orchestration platform like kubernetes is used?
UserDisplayName: 030
ThreadText: # Is Serf an added value when a container orchestration platform like kubernetes is used?
  
  (Asked by: username_0 on 2017-08-11)
  
  When the Hashicorp's website was checked it seems that there is another tool, i.e. Serf. Back in the day there was another tool called `otto`, but that was deprecated at a certain moment.
  
  After reading the [use cases](https://www.serf.io/intro/use-cases.html) I wonder whether it is an added value to use `serf` when a container orchestration platform like kubernetes is used.
  
  **Tags:** monitoring
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-08-15. Score: 4 | Accepted answer
  
  Serf is gossip protocol implementation and has absolutely nothing to do with orchestration tools like k8s. Even if such protocol is used internally, then in most cases it isn't available for you applications running in given orchestrator.
  
  So if your app or workflow depends on gossip protocol, then you will have use out of Serf, otherwise there is no point.
  
  ---
  
  [Gossip protocol](https://en.wikipedia.org/wiki/Gossip_protocol) is way of messaging to all nodes without:
  
  * Centralized point of knowledge
  * Single point of failure
  * Using whole network capability of any of the nodes
  
  In simple words it works like "message chains" ("If you do not send this to N people you will never find your love" or something like that).
  
  1. One node send notification to N out of M of its fellows
  2. If you receive message that you have already received, then do nothing.
  3. Otherwise go to step 1.
  
  Given such simple protocol you can calculate probability when all your nodes will receive message with 99% chance.
  
  
  ---
  
  