anemo
By MystenLabs
typed-protocols
Session types framework with support of protocol pipelining. (by input-output-hk)
anemo | typed-protocols | |
---|---|---|
1 | 2 | |
41 | 9 | |
- | - | |
4.6 | 7.3 | |
about 1 month ago | 11 days ago | |
Rust | Haskell | |
Apache License 2.0 | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
anemo
Posts with mentions or reviews of anemo.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-05.
-
On Implementation of Distributed Protocols
Communication layer in Sui is based on anemo, a peer-to-peer networking library built on top of QUIC. QUIC is a modern higher-level network transport protocol layered over UDP. It has built-in support for encryption and multiplexing. Similar to TCP connections, QUIC streams are reliable, ordered, bidirectional, providing flow control (backpressure), but they are cheap and almost instantaneous to open once an initial connection is established. The anemo library takes advantage of the efficient stream-multiplexing capability of QUIC; libp2p also uses the built-in capabilities of QUIC when it is used as a transport mechanism.
typed-protocols
Posts with mentions or reviews of typed-protocols.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-04-05.
-
On Implementation of Distributed Protocols
Certain correctness properties of code can be ensured statically, i.e. at compile time. Those checks rely on the programming language's type system. Software engineers can take advantage of type safety features to implement components in a way that makes them safe by construction. For example, Cardano uses the typed-protocols package, a generic framework for implementing application-level protocols, which is based on a simple form of session typing.6 Within this framework, protocols are described as state machines encoded into Haskell types. The allowed transitions between states correspond to messages exchanged between the peers, so the protocol state determines which messages are allowed to be sent or must be accepted when received, at type level. This simplifies protocol implementation, allows early detection of protocol violations, and makes the protocols themselves deadlock-free by construction. More advanced type-level programming techniques may allow achieving impressive levels of type safety; however, such code may be significantly harder to implement, understand, and maintain.
-
RPC lib?
I like to use typed-protocols for this: https://github.com/input-output-hk/typed-protocols/
What are some alternatives?
When comparing anemo and typed-protocols you can also consider the following projects:
nng-haskell - Haskell bindings for NNG (https://github.com/nanomsg/nng)
cardano-node - The core component that is used to participate in a Cardano decentralised blockchain. [Moved to: https://github.com/IntersectMBO/cardano-node]