memberlist
futures-rs
memberlist | futures-rs | |
---|---|---|
8 | 11 | |
3,506 | 5,239 | |
0.4% | 0.6% | |
4.8 | 8.4 | |
14 days ago | about 8 hours ago | |
Go | Rust | |
Mozilla Public License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
memberlist
- library for gossip coordination
-
Is it possible to have more than 1 master available for writes in a raft system?
I use lightweight https://github.com/hashicorp/memberlist to build initial cluster skeleton (find out what are nodes constituting it)
-
Leaderless consensus protocol in the wild
Does https://github.com/hashicorp/memberlist count? It’s a gossip-based eventual consistency protocol based on SWIM.
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
An equivalent of golang's memberlist would be awesome.
-
What's the biggest outage you have ever caused?
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.
-
Service discovery library in Rust?
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).
-
Ask HN: Which are the best go repositories to read to learn the language?
https://github.com/hashicorp/memberlist
Fairly idiomatic/clean
-
A Spanner-based distributed locking library
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.
futures-rs
-
Which async channel is best?
So this is actually better than true fairness (true fairness would lead to deadlock if a sender is forgotten). It is a pity that the there does not seem to be resources that document this design. There is this old thread where Carl provides some background, but I found it personally a bit hard to follow.
-
Async cancellation: a case study of pub-sub in mini-redis
Is this still true after it switched to using FuturesOrdered?
-
I don't really understand how I'm supposed to use async
Done.
-
Confused about how to use tokio to process a vector in parallel
You can use Streams, which are the async version of Iterators; They aren't stable yet, so you'll have to use a crate such as futures.
-
What crates would you consider essential?
futures
-
How to architect Rust code on Async/Await
For traits, like AsyncRead and AsyncWrite, go with the futures crate.
-
Async Rust in Practice: Performance, Pitfalls, Profiling
Here is the PR: https://github.com/rust-lang/futures-rs/pull/2551
Yield = wake the `waker_ref`. Avoiding the yield would be clone().wake().
That said, "poll immediately" isn't actually a thing nor was it ever a thing except in incorrect implementations.
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
Rust lacks an implementation of ReactiveX. futures/futures-signals seems to be the the ecosystem equivalent but I'm sure there'd be a lot of interest in an actual implementation.
-
Why isn't `rc::Weak<T>` marked `UnwindSafe`when T is `RefUnwindSafe`?
The opposite problem exists as well. Many types are actually unwind safe, but do not get the autotrait. In that case authors would have to manually declare them UnwindSafe. Because this is rarely done, having an API with a trait bound T: UnwindSafe is rarely viable in terms of ergonomics. It now obliges client code to wrap all calls to your API in AssertUnwindSafe which, if they use types from third party libraries, obliges them to assert this is fine. example
-
futures 0.3.9 released with big improvement in compile time
Also, we plan to give users more control in the future. See https://github.com/rust-lang/futures-rs/issues/2207, https://github.com/rust-lang/futures-rs/issues/2295, etc. for this
What are some alternatives?
rust - Official implementation of the IPGen Spec in Rust
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
hashring - Consistent hashing "hashring" implementation in golang (using the same algorithm as libketama)
async-std - Async version of the Rust standard library
spindle - A distributed locking library built on top of Cloud Spanner and TrueTime.
carboxyl - Functional Reactive Programming library for Rust
LiteDB - LiteDB - A .NET NoSQL Document Store in a single data file
mioco - [no longer maintained] Scalable, coroutine-based, fibers/green-threads for Rust. (aka MIO COroutines).
pjproject - PJSIP project
tangle - Deprecated - Use https://github.com/alexcrichton/futures-rs instead
groupcache - groupcache is a caching and cache-filling library, intended as a replacement for memcached in many cases.
coio-rs - Coroutine I/O for Rust