-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discovery and concensus: research and discussion. #184
Comments
Crypto pump is here: BFT options:
I'm currently working in a startup developing decentralized applications on the DPoS blockchain Telos, Its a fork of the bigger EOS blockchain. Some good things about it:
Basically every time you need for example, voting or an escrow you can write your backend in a smart contract and interact with it from python. The service discovery could be saved in a ledger inside a smart contract |
thanks @guilledk, got any links on performance tradeoffs by chance? No rush either. |
Hashicorp has some great, single binary (so deployment is not a challenge) solutions to:
Hashicorp Nomad
Hashicorp Consul
Hashicorp Consul also exposes their battle tested raft library https://github.com/hashicorp/raft |
This is a draft issue that I hope gets filled out more and more by lurkers over time.
The road map has the following:
But in order to do these things we need both a service discovery system (presumably by relying on a (set of) protocols) and, a modern concensus system which these days is usually in the form of either a centralized algo such as raft or, the thoroughly more pumped distributed equivalents.
Here are some resources to start poking at for research and tinkering:
RAFT
pumps:zero-conf protocols:
BFT variants:
As always, lurkers engage.
The text was updated successfully, but these errors were encountered: