I'm a little confused by the docs - is there a way to host the Deno KV datastore locally, or is the "run locally" option only for accessing a store hosted by Deno Land Inc on self-hosted hardware?
You can use Deno KV locally - the underlying tech is SQLite. It's as simple as writing code and you don't need to spin up any databases or setup any connections.
Data is always replicated to three of our "big" regions currently. Extending the list of storage regions and providing more flexible data distribution configuration is one of the next things we want to do.
> what about pricing?
During the closed beta it's free with a 1 GiB per project limit.
From the API docs (https://deno.land/api@v1.33.1?unstable&s=Deno.Kv): "Keys have a maximum length of 2048 bytes after serialization. Values have a maximum length of 64 KiB after serialization."
Pushing branch code in a Deploy enabled project automatically creates a branch deployment in Deploy (awesome feature by the way). Will this branch deployment share the same KV store as the main branch? Or does each separate branch build have their own KV store?
Engineer working on Deno KV here. Building on FDB is mostly a pleasant experience since it solves the hard part of the problem for us (concurrency control and persisting mutations).
We sometimes run into its limitations - the way we are using FDB is a bit beyond what it was originally designed for. But when it works, it works great.
11 comments
[ 3.3 ms ] story [ 36.3 ms ] threadIs the data stored in all regions at all times?
Also, what about pricing?
> Is the data stored in all regions at all times?
Data is always replicated to three of our "big" regions currently. Extending the list of storage regions and providing more flexible data distribution configuration is one of the next things we want to do.
> what about pricing?
During the closed beta it's free with a 1 GiB per project limit.
What's the size limit of a value?
All main deployments share a different store.
I've always thought it deserved to be used more widely so intrigued to see it pop up here.
We sometimes run into its limitations - the way we are using FDB is a bit beyond what it was originally designed for. But when it works, it works great.