Extend Chat Example w/ Gossip Based Backend #1120
Conversation
Deploying hydroflow with
|
| Latest commit: |
7271227
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9126cf52.hydroflow.pages.dev |
| Branch Preview URL: | https://rohit-randomized-gossip.hydroflow.pages.dev |
In one of the stand-ups, Joe suggested interop with the existing client as a goal. This seems like the easiest way to do that. What'd you have in mind? |
The current code supports letting readers see the distinction between single-server vs gossiping-server, and run either one from the command line. The README.md should talk that through in a bit more detail is all. |
This is done. The new readme can also be run straight from the IDE (at least IntelliJ at the moment, unsure what vscode does with |
rohitkulshreshtha
force-pushed
the
rohit_randomized_gossip
branch
from
575b4de
to
ffccdb5
Compare
Added a gossip-based backend for the chat example. The implementation is based on ["Epidemic algorithms for replicated database maintenance"](https://dl.acm.org/doi/epdf/10.1145/41840.41841). Specifically, it implements push-based "rumor-mongering" with a blind-coin removal process.
Also added a test for the gossip server.
rohitkulshreshtha
force-pushed
the
rohit_randomized_gossip
branch
from
05badc4
to
7271227
Compare
|
Only conventional commits didn't pass, so squashing and merging. Wondering if we should configure that check differently. |
Added a gossip-based backend for the chat example.
The implementation is based on "Epidemic algorithms for replicated database maintenance". Specifically, it implements push-based "rumor-mongering" with a blind-coin removal process.