Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
longquanzheng opened this issue Jan 11, 2024 · 2 comments

Comments

@longquanzheng
Copy link

longquanzheng commented Jan 11, 2024

hashicorp/memberlist#46 (comment)

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?

@eyazici90
Copy link

I was wondering the same thing and stumbled upon this issue :) Thanks for asking, @longquanzheng

The only things I found regarding the differences between these two libs were;

 what are the key difference in the implementation?

I am curious about the answer as well :)

@tristanmorgan
Copy link
Member

Here's a nice talk about how they build up on each other.

Everybody Talks: Gossip, Serf, memberlist, Raft, and SWIM in HashiCorp Consul

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants