mirror of
https://github.com/denoland/deno.git
synced 2024-12-22 15:24:46 -05:00
b1c685f4b7
This brings some of the HTTP/2 retry behavior from reqwest to `ext/fetch`. It will retry very specific HTTP/2 errors once, if the body is able to be used again. Closes #27332 |
||
|---|---|---|
| .. | ||
| 01_db.ts | ||
| Cargo.toml | ||
| config.rs | ||
| 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.