Proposal: Centralized Cache State Store #71
Conversation
This file contains 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
Signed-off-by: Whit Waldo <[email protected]>
Signed-off-by: Whit Waldo <[email protected]>
Signed-off-by: Whit Waldo <[email protected]>
Signed-off-by: Whit Waldo <[email protected]>
Signed-off-by: Whit Waldo <[email protected]>
Signed-off-by: Whit Waldo <[email protected]>
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.
This is the first of several long-standing proposals for building high-performance, narrowly tailored and purpose-built state management components to provide more focused abstractions to the current general purpose state store building block.
As a cache, typically implemented as a key/value store, is quite similar in principle to the existing key/value store Dapr features today, this proposal sheds the various optional APIs around the first generation implementation in favor of a small and specific signature built to target a select few providers for those developers that need key/value state abstraction to temporarily cache data, but would also like the benefits of abstracting out the specific provider used while realizing the inherent resiliency capabilities of Dapr.
I'd be happy to take ownership of building this out in both Dapr and within the .NET SDK and then start building out the proposal for another piece (perhaps blob, queue or documents).