Cloudflare KV
UnclaimedCreate a global, low-latency, key-value data storage for dynamic and performant applications.
Visit WebsiteFreemiumVisit Website
TL;DR - Cloudflare KV
- Global, low-latency key-value data storage.
- Optimized for high read volumes and caching.
- Integrates with Cloudflare Workers and offers a REST API.
Pricing: Free plan available
Best for: Growing teams
Pros & Cons
Pros
- Extremely low latency for reads, especially for hot keys.
- Globally distributed for high availability and performance.
- Cost-effective with a generous free tier.
- Seamless integration with Cloudflare Workers.
- Suitable for caching, configuration, and session data.
Cons
- Eventually consistent, not suitable for applications requiring strong immediate consistency.
- Limited write rate per unique key (1 write RPS).
- Operations via dashboard or CLI count as billable usage.
Preview
Key Features
Global data distributionLow-latency data retrievalKey-value storageWorkers Bindings for Cloudflare Workers integrationREST API for external applicationsPer-object time-to-live (TTL)Internal caching for frequently accessed keysWrangler CLI integration
Pricing
Freemium
Cloudflare KV offers a generous free tier with optional paid upgrades for advanced features.
About Cloudflare KV
By Toolradar Team·
Cloudflare Workers KV is a globally distributed, eventually consistent key-value data store designed for high-read volumes and low-latency access. It allows developers to store and retrieve data across Cloudflare's global network, making it ideal for building dynamic APIs and websites that require fast data access from anywhere in the world.
This product is particularly useful for scenarios like caching API responses, storing user configurations and preferences, or managing user authentication details. Its architecture is optimized for frequently read keys, which benefit from an internal cache, leading to typical latencies between 500µs and 10ms for "hot" keys. Developers can interact with Workers KV using Workers Bindings for direct integration with Cloudflare Workers or via a REST API for external applications, with SDKs available for TypeScript, Python, and Go.
Cloudflare Workers KV is part of a suite of Cloudflare storage options, complementing services like R2 for large object storage, Durable Objects for consistent stateful serverless workloads, and D1 for lightweight SQL databases. It's specifically recommended for session data, credentials, and configuration data that are read at high rates and do not require immediate consistency.
Reviews
No reviews yet. Be the first to review Cloudflare KV!
Explore More
Cloudflare KV FAQ
What are the primary use cases for Cloudflare Workers KV?
Cloudflare Workers KV is ideal for caching API responses, storing user configurations and preferences, and managing user authentication details. It excels in scenarios requiring high read volumes with low latency across a global network.
How can I interact with a Workers KV namespace from an external application?
You can access your Workers KV namespace from an external application using the REST API. Cloudflare provides pre-generated SDKs for TypeScript, Python, and Go to simplify integration.
What are the daily limits for key reads and writes on the Workers Free plan?
On the Workers Free plan, you are limited to 100,000 key reads per day and 1,000 key writes per day. All limits reset daily at 00:00 UTC.
Do operations performed through the Cloudflare dashboard or Wrangler CLI count towards billable usage?
Yes, any operations executed via the Cloudflare dashboard or the Wrangler command-line interface, including updating, deleting, or listing keys in a namespace, are counted as billable KV usage.
Does Cloudflare Workers KV charge for data transfer or egress?
No, Cloudflare Workers KV does not charge for data transfer or egress. This means you will not incur additional costs for data moving out of the KV store.
When should I choose Workers KV over other Cloudflare storage options like R2 or D1?
Workers KV is best suited for configuration data, service routing metadata, personalization, and session storage that require high read volumes and low-latency global reads. For large unstructured data without egress fees, R2 is more appropriate, while D1 is designed for lightweight SQL relational data.
Source: developers.cloudflare.com