180
points
otrack
Joined 133 karma
Professor in Computer Science at Institut Polytechnique de Paris
https://sites.google.com/site/0track
- Author here.
Lamport simply calls his protocol "Paxos" to refer to both the single‑decree and multi‑decree versions. This is also the case in his other works, e.g., "Fast Paxos" and "Generalized Paxos." The term "Multi‑Paxos" is a later community/industry shorthand for the repeated or optimized use of single‑decree Paxos.
- The situation is less dramatic than this article says.
https://edri.org/our-work/chat-control-what-is-actually-goin...
- 8 points
- 2 points
- 1 point
- 1 point
- 3 points
- 2 points
- 2 points
- 2 points
- 3 points
- 2 points
- 2 points
- 2 points
- On th topic, I would advice reading the boulangerie algorithm. An improved version of the original solution:
- sshell inherits the limitations of the FaaS infrastructure, including the time limit. Regarding the big data use case, more work is necessary to assess this, but the applications we have written so far were competing both in terms of efficiency and pricing (Section 5 in [1]).
[1] https://drive.google.com/file/d/1D7h0hoMep0W73XV_EdXPSEWUxpT...
- Very interesting work, thanks for the link! We actually missed it among the references in our paper [1] and will correct this in the journal version. Regarding the differences, lsh has an interactive mode but not sshell. On the other hand, sshell compile to native (to support massively parallel calls), and IPCs between such calls (thanks to the DSO layer).
[1] https://drive.google.com/file/d/1D7h0hoMep0W73XV_EdXPSEWUxpT...
- 64 points
- 2 points
- 2 points
- 2 points
Once the specification is ready, I'll post about it here. :)
[1] https://arxiv.org/abs/1906.10917