raft
rust-libp2p
raft | rust-libp2p | |
---|---|---|
4 | 31 | |
532 | 4,165 | |
6.2% | 1.3% | |
8.8 | 9.8 | |
17 days ago | 3 days ago | |
Go | Rust | |
Apache License 2.0 | MIT License |
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.
raft
-
On Implementation of Distributed Protocols
etcd Raft — a library for maintaining replicated state machines (written in Go);
- Leader election library
-
Implementing a distributed key-value store on top of implementing Raft in Go
Have you seen this implementation? https://github.com/etcd-io/raft. I’ve used this as a starting point for our consensus with various services.
-
"In HPA, multiple pods may perform duplicate operations and cause data inconsistency?"
This is usual in parallel and distributed systems. For k8s, I recommend you either use Apache Zookeeper to coordinate “logical locks” for operations across pods or use the RAFT consensus protocol for scenarios where you need coordination amongst pods. For context, k8s itself uses the RAFT consensus protocol for etcd; see https://github.com/etcd-io/raft
rust-libp2p
-
On Implementation of Distributed Protocols
Substrate and Lighthouse use libp2p as a networking stack for communication between nodes. The libp2p framework is a versatile modular peer-to-peer networking stack. It provides a collections of abstractions, mechanisms, and protocols for facilitating communication in P2P systems. In particular, libp2p supports multiple transport mechanisms (TCP, QUIC, WebSocket, WebTransport, etc.), encryption schemes (TLS and Noise), and stream multiplexing. Higher-level protocols in libp2p are implemented on top of reliable, ordered, bidirectional binary streams, which are transparently encrypted and multiplexed by the framework.
-
Bifrost: A peer-to-peer communications engine with pluggable transports
It's a peer-to-peer "engine" with switchable components. Seems to run on different platforms (browsers, mobile, desktop, server).
At a glance, it looks pretty much like libp2p (https://libp2p.io/) but seems to integrate with libp2p as well (meaning you should be able to use Bifrost on one end, and libp2p on the other), so I'm guessing there is at least some fundamental difference, but I cannot spot it. Seems to use slightly different terminology compared to libp2p.
- Libp2p – A Modular Network Stack
- [AskJS] Any js browser based p2p libraries?
-
Decentralized Databases: ComposeDB
ComposeDB is a graph database created by 3BoxLabs, a company well-known in the Web3 ecosystem for their work on decentralized identifiers (DIDs) and their main product the Ceramic network. Ceramic is a network of nodes that store and share composable data streams on top of libp2p, the network stack that also powers IPFS.
-
What about a Zig implementation of lib2p2?
Yes, there is already a Rust version (https://github.com/libp2p/rust-libp2p) that behaves well at this level but I think we can reach a higher level of performance on this point with Zig. Also, if you look at the long term roadmap of libp2p (https://github.com/libp2p/specs/blob/master/ROADMAP.md), the mobile devices and IoT integrations for example are part of the considerations.
-
A Rust client library for interacting with Microsoft Airsim https://github.com/Sollimann/airsim-client
libp2p
-
Social Media on the Decentralized Web
At Filecoin Foundation, we see the technologies in the Filecoin ecosystem offering rock-steady stepping stones to this better future. Libp2p lets individual users find and talk to each other, without needing central servers. IPFS gives new services a way to find data, wherever it is stored — freeing them from dependence on one social media company over another and letting users move from one service to another. The Filecoin network itself, with incentivized storage, not only provides a provably stable basis for hosting content, but also shines a light on the kind of incentive systems that will enable independent social media to sustain and provide for itself for the long run, without relying on the largesse of the current tech giants.
-
Good sources to learn about IPFS?
Maybe https://libp2p.io
-
Fula: a new, innovative way to develop decentralized applications
So, after rolling my eyes and saying to myself 'not another web3 protocol', I began to understand the need for something new that not only takes advantage of the cutting edge in peer to peer networking but also acknowledges the fact that the client-server architecture is also not going away (which is incredibly important in a world full of low-powered, embedded devices).
What are some alternatives?
rqlite - The lightweight, distributed relational database built on SQLite.
cosmos-sdk - :chains: A Framework for Building High Value Public Blockchains :sparkles:
etcd - Distributed reliable key-value store for the most critical data of a distributed system
go-livepeer - Official Go implementation of the Livepeer protocol
Atomix - A Kubernetes toolkit for building distributed applications using cloud native principles
y-crdt - Rust port of Yjs
dragonboat - A feature complete and high performance multi-group Raft library in Go.
freenet-core - Declare your digital independence
etcd - Distributed reliable key-value store for the most critical data of a distributed system [Moved to: https://github.com/etcd-io/etcd]
consensus-specs - Ethereum Proof-of-Stake Consensus Specifications
rawkv - Cloud-native distributed key-value database.
rust-crdt - a collection of well-tested, serializable CRDTs for Rust