[Functions] Refactor Context and State API to allow plugging different state store implementations #8537
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.
[Functions] Refactor Context and State API to allow plugining different state store implementations
This change is based on #8530
Motivation
Currently the state API is tied to bookkeeper table implementation. For users who already run a database, it
might be useful to allow users to configure to use a different state store backend.
This change refactors the context and state API to allow plugining different state store implementations