foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-21 15:04:11 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/ext/kv
History
denobot 6267905f09
chore: forward v1.45.5 release commit to main (#24818)
2024-07-31 15:14:27 -07:00
..
01_db.ts fix(runtime): use more null proto objects (#23921) 2024-05-23 00:03:35 +02:00
Cargo.toml chore: forward v1.45.5 release commit to main (#24818) 2024-07-31 15:14:27 -07:00
dynamic.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
interface.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
lib.rs chore: update denokv_* crates (#23949) 2024-05-23 16:35:16 +02:00
README.md fix(docs): fix some deno.land/manual broken urls (#24557) 2024-07-15 11:08:45 +00:00
remote.rs Reland "refactor(fetch): reimplement fetch with hyper instead of reqwest" (#24593) 2024-07-18 01:37:31 +02:00
sqlite.rs chore: upgrade to rust 1.79 (#24207) 2024-06-14 17:10:57 +05:30

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.