development/deno
development/deno
1
0
Fork 0
mirror of https://github.com/denoland/deno synced 2024-11-05 18:45:24 +00:00
Code Issues Projects Releases Packages Wiki Activity
deno/ext/kv
History
Leo Kettmeir df879f9f74
chore: cleanup unused dependencies (#23787)
2024-05-13 14:23:39 -07:00
..
01_db.ts refactor: migrate extensions to virtual ops module (#22135) 2024-01-26 23:46:46 +01:00
Cargo.toml chore: cleanup unused dependencies (#23787) 2024-05-13 14:23:39 -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 perf(cli): use faster_hex (#22761) 2024-03-07 10:00:43 -07:00
README.md chore: update ext/kv to use denokv_* crates (#20986) 2023-10-31 11:13:57 +00:00
remote.rs refactor(ext/tls): Implement required functionality for later SNI support (#23686) 2024-05-09 10:54:47 -06:00
sqlite.rs chore: update copyright to 2024 (#21753) 2024-01-01 19:58:21 +00:00
time.rs refactor: use chrono::DateTime::from_timestamp (#23273) 2024-04-08 21:46:54 +00: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.