What is the write limit for a single Cloudflare KV key?

Cloudflare KV supports a maximum of 1 write per second per key. Exceeding this rate will trigger a 429 Too Many Requests error, which is why this skill includes retry logic with exponential backoff.

When should I use KV vs Durable Objects?

Use KV for read-heavy workloads (100:1 read/write ratio) where eventual consistency is fine. Use Durable Objects when you need strong consistency, atomicity, or real-time coordination.

How long does global propagation take for KV updates?

KV is eventually consistent. While writes are immediately visible in the same edge location, it can take up to 60 seconds (or the duration of your cacheTtl) to propagate globally.

What are the maximum size limits for KV data?

Keys are limited to 512 bytes, values can be up to 25 MiB, and metadata is restricted to 1024 bytes per entry.

Cloudflare Workers KV

Name: Cloudflare Workers KV
Author: jezweb

byjezweb

•

117

Database Management

Manages global key-value storage for Cloudflare Workers with optimized patterns for edge caching and high-performance data retrieval.

About

The cloudflare-kv skill equips Claude with the domain-specific knowledge required to implement and manage Cloudflare's globally distributed key-value storage. It provides expert guidance on handling eventual consistency, metadata optimization, and platform-specific limitations like the 1-write-per-second rate limit. This skill is ideal for developers building high-performance applications that require low-latency data access at the edge, offering production-ready patterns for caching, pagination, and bulk operations using the Wrangler CLI and Workers API.

Key Features

Metadata optimization strategies to reduce API calls and latency
Advanced caching logic using cacheTtl for read-heavy workloads
117 GitHub stars
Comprehensive Wrangler CLI reference for namespace and key management
Built-in patterns for exponential backoff and 429 rate limit handling
Expert implementation of KV CRUD operations with proper type safety

Use Cases

Caching API responses and expensive computations at the network edge
Storing user preferences and session data for low-latency retrieval
Managing global configuration, feature flags, and environment toggles

About

Key Features

Metadata optimization strategies to reduce API calls and latency
Advanced caching logic using cacheTtl for read-heavy workloads
117 GitHub stars
Comprehensive Wrangler CLI reference for namespace and key management
Built-in patterns for exponential backoff and 429 rate limit handling
Expert implementation of KV CRUD operations with proper type safety

Use Cases

Caching API responses and expensive computations at the network edge
Storing user preferences and session data for low-latency retrieval
Managing global configuration, feature flags, and environment toggles