Deno/deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-21 20:38:55 +00:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity
3f26310728
deno/ext/kv
History
Sahand Akbarzadeh 032ae7fb19
feat(ext/fetch): allow embedders to use hickory_dns_resolver instead of default GaiResolver (#26740) 
Allows embedders to use `hickory-dns-resolver` instead of threaded "getaddrinfo" resolver
in the `fetch()` implementation.
2024-11-15 11:44:11 +01:00
..
01_db.ts refactor(ext/kv): align error messages (#25500) 2024-09-19 13:20:09 +05:30
Cargo.toml chore: forward v2.0.6 release commit to main (#26804) 2024-11-10 13:12:18 +05:30
config.rs chore: make fields public on PermissionDeniedError and deno_kv::KvConfig (#26798) 2024-11-12 17:49:49 +00:00
dynamic.rs
interface.rs
lib.rs refactor(ext/kv): use concrete error type (#26239) 2024-10-17 17:59:02 +00:00
README.md
remote.rs feat(ext/fetch): allow embedders to use hickory_dns_resolver instead of default GaiResolver (#26740) 2024-11-15 11:44:11 +01:00
sqlite.rs refactor(runtime/permissions): use concrete error types (#26464) 2024-11-04 09:17:21 -08:00

README.md

deno_kv

This crate provides a key/value store for Deno. For an overview of Deno KV, please read the manual.

Storage Backends

Deno KV has a pluggable storage interface that supports multiple backends:

  • SQLite - backed by a local SQLite database. This backend is suitable for development and is the default when running locally. It is implemented in the denokv_sqlite crate.
  • Remote - backed by a remote service that implements the KV Connect protocol, for example Deno Deploy.

Additional backends can be added by implementing the Database trait.

KV Connect

The KV Connect protocol allows the Deno CLI to communicate with a remote KV database. The specification for the protocol, and the protobuf definitions can be found in the denokv repository, under the proto directory.