mirror of
https://github.com/denoland/deno.git
synced 2024-12-21 23:04:45 -05:00
8db420d552
Reland of https://github.com/denoland/deno/pull/24056 that doesn't suffer from the problem that was discovered in https://github.com/denoland/deno/pull/24261. It uses upgraded `hyper` and `hyper-util` that fixed the previous problem in https://github.com/hyperium/hyper/pull/3691. |
||
|---|---|---|
| .. | ||
| 01_db.ts | ||
| Cargo.toml | ||
| dynamic.rs | ||
| interface.rs | ||
| lib.rs | ||
| README.md | ||
| remote.rs | ||
| sqlite.rs | ||
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.