feat(keystore) Define Branch Key Store read consistency semantics #302
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
brandondahler
force-pushed
the
features/ReadConsistencySemantics
branch
from
089a311 to
b31b4cd
Compare
seebees
reviewed
Jul 25, 2025
changes/2025-07-24_define-branch-key-store-read-consistency-semantics/background.md
Outdated
Show resolved
Hide resolved
…mantics/background.md Co-authored-by: seebees <[email protected]>
seebees
reviewed
Jul 25, 2025
| The [branch key store](../../framework/branch-key-store.md) persists branch key versions | ||
| in a persistent data store such as a DynamoDb table. | ||
|
|
||
| These distributed data stores often offer configurable read consistency, |
There was a problem hiding this comment.
For posterity, this is sometimes referred to as "read after write". Which is the specific kind of consistency we are after here.
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.
Issue #, if available:
CrypTool-5363
Description of changes:
Updates specification to clarify
ConsistentReadbehavior for the Branch Key Store and provide an option for agents to configure that consistent reads are to be used.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Check any applicable: