hashicorp / hashicorp/serf

Using as a library of managing membership, Is serf just provides a different/better implementation of memberlist?

Open
#712 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
6.1k
Forks
609
Avg merge
15h 1m
Merged PRs (30d)
3

Description

https://github.com/hashicorp/memberlist/issues/46#issuecomment-127439840

I found some comments here quite useful, but wanted to know more about the difference/decisions about the two projects:

AFAIK:
* memberlist is a library for managing cluster membership. It implements the gossip protocol.
* serf depends on memberlist. Even the serf.Config depends on memberlist.Config

serf seems provides more functionalities but if I just use as managing membership, what are the key difference in the implementation?

Or a big part of my question is -- why does serf depend on memberlist?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.