Cherry-Node
bastion
Cherry-Node | bastion | |
---|---|---|
2 | 15 | |
75 | 2,759 | |
- | 0.4% | |
0.0 | 0.0 | |
about 1 month ago | about 1 year ago | |
Rust | Rust | |
Apache 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.
Cherry-Node
-
The next few weeks will be exciting for Cherry
🖥 Mainnet: Cherry Chain (Launched April) https://github.com/CherryNetwork/Cherry-Node/releases/tag/monthly-2022-04
- Seraphim: Release 0.0.24 tagged. Our testnet just dropped. Find the fully open sourced node implementation here: https://cher.to/node A user interface will follow. Explore the code, let us know what you think. Welcome to the year of Cherry
bastion
- Write Elixir NIFs in Rust
- Bastion – Highly-Available Distributed Fault-Tolerant Runtime for Rust
-
lunatic v0.9 released - Bringing Erlang's supervisors to Rust
How is this better / different than https://github.com/bastion-rs/bastion ?
-
Introspection in Erlang/BEAM-inspired Async-Rust-Executors?
There are attempts to implement an Erlang/BEAM-inspired reactor/runtime/executor/ecosystem for Rust's Async, in particular Bastion. (There are also Lumen, Lunatic and Async-Backplane/Async-Supervisor.)
- What is the current state of actor systems in Rust?
-
Announcing "Zestors": A simple, fast and flexible actor-framework
I would be interested in an example showing how to build a robust runtime like bastion with fault tolerance.
-
Async feedback from 2 years of usage
But the issue you're referring to, building a fault-tolerant web server where you can have granular control over killing background jobs regardless if they're blocked on a syscall, totally requires using this kind of software architecture. See Bastion.
-
Can one code different kind of multithreading paradigms in Rust (BEAM, Node, Go)?
Bastion, a Rust async runtime inspired by the beam distribution and supervision model
-
Linus Torvalds on Rust support in kernel
I don't really know much about erlang, but I think this may be along the lines of what you are thinking of: https://github.com/bastion-rs/bastion
(I also don't really think the linux kernel people would be interested...)
-
Lunatic - An Erlang inspired runtime for all programming languages
This reminds me of bastion. Looks like it attempts to fulfill the same needs, though I guess Lunatic has native WASM support whereas bastion might require some tweaking to have it work? Haven't worked with bastion, so that part of harder time with WASM is just a wild speculation. On the other hand bastion looks much more mature. Probably /u/vertexclique could give a more informed opinion about the difference between the two ;) I really like what these projects are putting forward.
What are some alternatives?
actix - Actor framework for Rust.
smol - A small and fast async runtime for Rust
lunatic - Lunatic is an Erlang-inspired runtime for WebAssembly
tiny-tokio-actor - A simple tiny actor library on top of Tokio
rustig - A tool to detect code paths leading to Rust's panic handler
riker - Easily build efficient, highly concurrent and resilient applications. An Actor Framework for Rust.
async-backplane - Simple, Erlang-inspired fault-tolerance framework for Rust Futures.
lumen - An alternative BEAM implementation, designed for WebAssembly
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
wactor - Ultra minimal actor API wrapper for lunatic
libco - libco is a coroutine library which is widely used in wechat back-end service. It has been running on tens of thousands of machines since 2013.
Coerce-rs - Actor runtime and distributed systems framework for Rust