Skip to content

Commit 8da1325

Browse files
committed
Setting up one large FAQ page.
1 parent 02923e7 commit 8da1325

File tree

2 files changed

+44
-15
lines changed

2 files changed

+44
-15
lines changed

src/content/docs/kv/faq.mdx

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: FAQ
3+
pcx_content_type: faq
4+
sidebar:
5+
order: 8
6+
7+
---
8+
9+
import { Glossary } from "~/components"
10+
11+
Frequently asked questions regarding Workers KV.
12+
13+
### General
14+
15+
#### Can I use Workers KV without using Workers?
16+
17+
Yes, you can use Workers KV outside of Workers by using the [REST API](/api/resources/kv/) or the associated Cloudflare SDKs for the REST API. It is important to note the [limits of the REST API](/fundamentals/api/reference/limits/) that apply.
18+
19+
#### Why can I not immediately see the updated value of a key-value pair?
20+
21+
Workers KV heavily caches data across the Cloudflare network. Therefore, it is possible that you read a cached value for up to the cache TTL duration.
22+
23+
#### Is KV eventually consistent or strongly consistent?
24+
25+
Workers KV stores data in central stores and replicates the data to all Cloudflare locations through a hybrid push/pull replication approach. This means that the previous value of the key-value pair may be seen in a location for as long as the cache TTL.
26+
27+
This means that KV is eventually consistent.
28+
29+
Refer to [How KV works](/kv/concepts/how-kv-works/).
30+
31+
### Pricing
32+
33+
#### When writing via KV's [REST API](/api/resources/kv/subresources/namespaces/methods/bulk_update/), how are writes charged?
34+
35+
Each key-value pair in the `PUT` request is counted as a single write, identical to how each call to `PUT` in the Workers API counts as a write. Writing 5,000 keys via the REST API incurs the same write costs as making 5,000 `PUT` calls in a Worker.
36+
37+
#### Do queries I issue from the dashboard or wrangler (the CLI) count as billable usage?
38+
39+
Yes, any operations via the Cloudflare dashboard or wrangler, including updating (writing) keys, deleting keys, and listing the keys in a namespace count as billable KV usage.
40+
41+
#### Does Workers KV charge for data transfer / egress?
42+
43+
No.
44+

src/content/docs/kv/platform/pricing.mdx

Lines changed: 0 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -10,18 +10,3 @@ import { Render } from "~/components"
1010

1111
<Render file="kv_pricing" product="workers" />
1212

13-
## Frequently Asked Questions
14-
15-
Frequently asked questions related to KV pricing:
16-
17-
* When writing via KV's [REST API](/api/resources/kv/subresources/namespaces/methods/bulk_update/), how are writes charged?
18-
19-
Each key-value pair in the `PUT` request is counted as a single write, identical to how each call to `PUT` in the Workers API counts as a write. Writing 5,000 keys via the REST API incurs the same write costs as making 5,000 `PUT` calls in a Worker.
20-
21-
* Do queries I issue from the dashboard or wrangler (the CLI) count as billable usage?
22-
23-
Yes, any operations via the Cloudflare dashboard or wrangler, including updating (writing) keys, deleting keys, and listing the keys in a namespace count as billable KV usage.
24-
25-
* Does Workers KV charge for data transfer / egress?
26-
27-
No.

0 commit comments

Comments
 (0)