Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support schema/migrations for binary encoding #95

Open
tmpfs opened this issue Aug 26, 2022 · 1 comment
Open

Support schema/migrations for binary encoding #95

tmpfs opened this issue Aug 26, 2022 · 1 comment
Assignees

Comments

@tmpfs
Copy link
Collaborator

tmpfs commented Aug 26, 2022

Possibly use Protobuf/CapNProto/Thrift or Avro.

So that we could change the binary encoding for vaults in future versions with backwards compatibility and offer tools to migrate from binary encoding versions.

@tmpfs tmpfs self-assigned this Aug 26, 2022
@tmpfs
Copy link
Collaborator Author

tmpfs commented Jan 13, 2023

My current thinking on this is that we leverage webassembly to solve this problem.

Move the encoder and decoder routines to WASM modules and then we can bundle different webassembly modules for different versions of the binary schema which can be used to migrate between versions.

This will likely add significant overhead to the encoding and decoding of vaults and to support VaultFileAccess would need to be wasm32-wasi compatible.

For the planned plugin architecture we will need a webassembly runtime so it is already expected that we add that dependency.

@tmpfs tmpfs pinned this issue Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant