foster/denoland-deno
0
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-10-29 08:58:01 -04:00
Code Issues Wiki Activity
denoland-deno/ext/kv
History
Igor Zinkovsky 86769b0d1c
feat(ext/kv) add backoffSchedule to enqueue (#21474) 
Also reduces the time to run `kv_queue_undelivered_test.ts` test from
100 seconds down to 3 seconds.

closes #21437
2023-12-12 22:51:23 -08:00
..
01_db.ts feat(ext/kv) add backoffSchedule to enqueue (#21474) 2023-12-12 22:51:23 -08:00
Cargo.toml chore: forward v1.38.5 release commit to main (#21472) 2023-12-06 00:53:16 +00: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 feat(ext/kv) add backoffSchedule to enqueue (#21474) 2023-12-12 22:51:23 -08:00
README.md chore: update ext/kv to use denokv_* crates (#20986) 2023-10-31 11:13:57 +00:00
remote.rs feat(unstable): kv.watch() (#21147) 2023-12-05 21:21:46 +08: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.