Under the hood, does DenoKV implement an abstraction that specializes locally to SQLite and to Deno Deploy in the cloud? Or are DenoKV local and DenoKV cloud two separate products with a common public API?
When you use it locally the database is only on your device however all deno processes can access the same dB so you can use it to pass data around just like you can for localStorage that deno also supports.
When you use it in the cloud (deno deploy) then saves are replicated across regions.
Deploy is server less.
KV is simply a wrapper around sqlite with that you get atomic transactions that you wouldn't with local storage
The API is standardized for both.