From the docs on the latest KV release:
Deno KV is currently experimental and subject to change. While we do our best to ensure data durability, data loss is possible, especially around Deno updates. We recommend that you backup your data regularly and consider storing data in a secondary store for the time being
https://dotland.deno.dev/manual@v1.33.1/runtime/kv
This is a very serious note, however, there are no specifics about how this data loss may occur, and the only interpretation that I can take as a cautious person is that I cannot trust KV with any kind of sensitive data at any time because I could never guess if some piece has been lost or not.
I would like to know if my interpretation is correct, if there is something that can be done to mitigate the issue such that it does not impact critical data, and if there's some kind of expected release and date at which this would be resolved. At this time I don't know whether to expect this issue to exist within the following months to come, or years to come.
I would like to use Deno KV on Deno Deploy, everything about it seems ideal, except for this single warning, which is a an absolute show-stopper.
Thanks
From the docs on the latest KV release:
This is a very serious note, however, there are no specifics about how this data loss may occur, and the only interpretation that I can take as a cautious person is that I cannot trust KV with any kind of sensitive data at any time because I could never guess if some piece has been lost or not.
I would like to know if my interpretation is correct, if there is something that can be done to mitigate the issue such that it does not impact critical data, and if there's some kind of expected release and date at which this would be resolved. At this time I don't know whether to expect this issue to exist within the following months to come, or years to come.
I would like to use Deno KV on Deno Deploy, everything about it seems ideal, except for this single warning, which is a an absolute show-stopper.
Thanks