search

WebAssembly / wasi-keyvalue

27 stars 10 forks source link

feat(*): major updates to the keyvalue interfaces #30

Closed Mossaka closed 5 months ago

Mossaka commented 7 months ago

This commit has changed many function signatures to account for the scenario where the key does not exist. Instead of returning an error for non-existance keys, the expected behvaior should be returning a none for the client to handle.

The other changes are for providing more clarity to the behavior of the APIs ine wasi:keyvalue interfaces. It explained what it means to have batch operations without guarantees to atomicity and what are atomic operations like CAS.

It also changed the portability criteria to follow the newest WASI proposal template, and added a new goal regarding keyvalue operation performance in this proposal.

It also changed the readwrite and batch interface names to eventual and eventual-batch to indicate the operations are expected to run in an eventual consistent platform.

Closes #24 #25 #9

Mossaka commented 6 months ago

Could you PTAL? @lukewagner

Mossaka commented 5 months ago

Could you please take another look, @lukewagner?