proposal doc for staging with a queue #1685
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arielshaqed
requested review from
guy-har,
itaiad200,
johnnyaug,
nopcoder,
ozkatz and
talSofer
arielshaqed
force-pushed
the
docs/design-staging-with-a-queue
branch
from
fc4672e to
6126a40
Compare
arielshaqed
force-pushed
the
docs/design-staging-with-a-queue
branch
from
6126a40 to
d8e0c4a
Compare
arielshaqed
changed the title
nopcoder
approved these changes
May 10, 2021
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Very preliminary "let's do Raft (or Kinesis)" design doc. Happy to hear opinions.
It is actually quite similar to Oz' "S3 + kv store" proposal: batching to improve performance, staging tokens, a degree of optimism when writing.
Assuming no gaping holes, the next stage is to analyze expected performance, cost of queue (if Kinesis), and differences.