-
Notifications
You must be signed in to change notification settings - Fork 66
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
Automatic network setup #32
Comments
scuttlebutt doesnt care about the network. Its just a replication stream over any IO. The network topology you choose depends on what trade offs you want to make in terms of latency, saturation & stability against partitions. I started topology a while ago to document various options available to you. Since scuttlebutt is a gossip protocol, it has eventual consistency irregardless of your network topology as long as it's not permanently split. |
yes, @Raynos is exactly right. |
@mcollina did you ever find a solution to this? It seems that it would be possible to do this using bittorrent-protocol with the ut_pex extension to enable peer exchange. |
Scuttlebutt is all about streams, but I have to setup the network in a way where everybody 'knows' everybody else ip/port combination. Should a network be fully connected, or connected just to N/2 + 1 nodes?
This seems a very common setup. Do you know if this is already implemented somewhere?
The text was updated successfully, but these errors were encountered: