foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-30 16:40:57 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/ext/kv
History
Matt Mastracci 936d265f8a
perf: remove opAsync (#21690) 
`opAsync` requires a lookup by name on each async call. This is a
mechanical translation of all opAsync calls to ensureFastOps.

The `opAsync` API on Deno.core will be removed at a later time.
2024-01-04 20:34:48 +01:00
..
01_db.ts perf: remove opAsync (#21690) 2024-01-04 20:34:48 +01:00
Cargo.toml 1.39.1 (#21667) 2023-12-21 16:46:13 +01:00
dynamic.rs feat(unstable): kv.watch() (#21147) 2023-12-05 21:21:46 +08:00
interface.rs chore: update ext/kv to use denokv_* crates (#20986) 2023-10-31 11:13:57 +00:00
lib.rs fix(unstable): kv watch should stop when db is closed (#21665) 2024-01-04 20:34:46 +01:00
README.md chore: update ext/kv to use denokv_* crates (#20986) 2023-10-31 11:13:57 +00:00
remote.rs feat(unstable): only allow http2 for kv remote backend (#21616) 2024-01-04 20:34:46 +01:00
sqlite.rs feat(unstable): kv.watch() (#21147) 2023-12-05 21:21:46 +08:00
time.rs chore: remove usage of chrono::Utc::now() (#20995) 2023-10-30 11:45:45 -04: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.