Tenant persistence with in-memory key-value storage #144
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
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 PR introduces logic to persist a tenant using an in-memory key-value storage. Later on, we'll switch to a PostgreSQL backend for both development and likely production.
It also kicks off a refactor to employ schemas for generating domain types. This approach will enable us to use these schemas to encode and decode information from the storage backend, thereby increasing type safety at runtime.
However, this PR does not yet include data encryption. Nonetheless, in 99% of cases, data should be encrypted because the storage backend may be located outside the engine's boundary, making it an untrustable component.
Key-value Storage
We've opted for a key-value model for the storage backend due to its simplicity. This choice was largely inspired by HashiCorp Vault's storage model. Given that Narval might not control the storage backend, using a straightforward key-value system simplifies supporting multiple types of persistence layers with minimal effort – it's relatively easy to construct a kv data model almost anywhere.