Skip to content
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.

Commit

Permalink
docs: add key expiration (#731)
Browse files Browse the repository at this point in the history
* docs: add key expiration

* fix typeck
  • Loading branch information
losfair committed Sep 14, 2023
1 parent 98d0bbe commit cb9b96d
Show file tree
Hide file tree
Showing 2 changed files with 54 additions and 1 deletion.
52 changes: 52 additions & 0 deletions runtime/kv/key_expiration.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
# Key Expiration

> ⚠️ Deno KV is currently **experimental** and **subject to change**. While we do
> our best to ensure data durability, data loss is possible, especially around
> Deno updates. We recommend that you backup your data regularly and consider
> storing data in a secondary store for the time being.
> 🌐 Deno KV is available for Deno Deploy.
> [Read the Deno Deploy KV docs](https://deno.com/deploy/docs/kv).
Since version 1.36.2, Deno KV supports key expiration. This allows an expiration
timestamp to be associated with a key, after which the key will be automatically
deleted from the database:

```ts,ignore
const kv = await Deno.openKv();
// `expireIn` is the number of milliseconds after which the key will expire.
function addSession(session: Session, expireIn: number) {
await kv.set(["sessions", session.id], session, { expireIn });
}
```

Key expiration is supported on both Deno CLI and Deno Deploy.

## Atomic expiration of multiple keys

If multiple keys are set in the same atomic operation and have the same
`expireIn` value, the expiration of those keys will be atomic. For example:

```ts,ignore
const kv = await Deno.openKv();
function addUnverifiedUser(
user: User,
verificationToken: string,
expireIn: number,
) {
await kv.atomic()
.set(["users", user.id], user, { expireIn })
.set(["verificationTokens", verificationToken], user.id, { expireIn })
.commit();
}
```

## Caveats

The expire timestamp specifies the _earliest_ time after which the key can be
deleted from the database. An implementation is allowed to expire a key at any
time after the specified timestamp, but not before. If you need to strictly
enforce an expiration time (e.g. for security purposes), please also add it as a
field of your value and do a check after retrieving the value from the database.
3 changes: 2 additions & 1 deletion toc.json
Original file line number Diff line number Diff line change
Expand Up @@ -143,7 +143,8 @@
"operations": "Operations",
"transactions": "Transactions",
"secondary_indexes": "Secondary indexes",
"key_space": "Key Space"
"key_space": "Key Space",
"key_expiration": "Key Expiration"
}
},
"location_api": "Location API",
Expand Down

0 comments on commit cb9b96d

Please sign in to comment.