You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/kv/faq.mdx
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,25 +20,24 @@ Yes, you can use Workers KV outside of Workers by using the [REST API](/api/reso
20
20
21
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
22
23
-
### Is KV eventually consistent or strongly consistent?
23
+
### Is Workers KV eventually consistent or strongly consistent?
24
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.
25
+
Workers KV is eventually consistent.
26
26
27
-
This means that KV is eventually consistent.
27
+
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. This means that Workers KV is eventually consistent.
28
28
29
29
Refer to [How KV works](/kv/concepts/how-kv-works/).
30
30
31
31
## Pricing
32
32
33
-
### When writing via KV's [REST API](/api/resources/kv/subresources/namespaces/methods/bulk_update/), how are writes charged?
33
+
### When writing via Workers KV's [REST API](/api/resources/kv/subresources/namespaces/methods/bulk_update/), how are writes charged?
34
34
35
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
36
37
37
### Do queries I issue from the dashboard or wrangler (the CLI) count as billable usage?
38
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.
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 Workers KV usage.
40
40
41
41
### Does Workers KV charge for data transfer / egress?
0 commit comments