spec VS memberlist

This is definitely not what you are looking for but I thought it might be interesting to mention my "service determination" (opposite of service discovery but trying to achieve the same goal) toy as well :) Five years ago, I wrote the IPGen Spec (https://github.com/ipgen/spec) which outlines a way to generate unique and reproducible IP addresses in a stateless manner. Naturally, it can be used for service discovery.

hashicorp/memberlist: go get -u github.com/hashicorp/memberlist

I use lightweight https://github.com/hashicorp/memberlist to build initial cluster skeleton (find out what are nodes constituting it)

Does https://github.com/hashicorp/memberlist count? It’s a gossip-based eventual consistency protocol based on SWIM.

An equivalent of golang's memberlist would be awesome.

I don't know the engineer that did it but I know what happened. There's a library that a bunch of foundational Amazon services use called DFDD. It uses a gossip protocol to handle service discovery and health checking. The open source equivalent is Hashicorp memberlist. To remove a node from the cluster, you have to send a command to an arbitrary node that says a node is dead.

serf uses memberlist which uses the SWIM failure detection protocol (https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf) with the Lifeguard extensions (https://arxiv.org/pdf/1707.00788.pdf).

https://github.com/hashicorp/memberlist

Fairly idiomatic/clean

This algorithm assumes you're doing that separately using some sort of membership protocol (e.g. SWIM), and you pass in the membership list that you are keeping up to date with that protocol. If you're curious about those, HashiCorp memberlist and HashiCorp Serf are really good to look at. I believe Consul uses those libraries under the hood.