cloudflare-kv

Global caching with Cloudflare Workers uses key-value storage to cache API responses across 300+ edge locations. Store responses with TTL expiration (minimum 60 seconds) to automatically serve cached data, reducing latency and backend load. This Skill handles get, put, and TTL management for read-through and write-through caching patterns.

Cloudflare KV enforces strict limits: keys are 512 bytes maximum, values up to 25 MiB, metadata up to 1024 bytes, minimum 60-second TTL, and 1 write per second per key. This Skill manages these constraints and handles rate limit errors to prevent operations from failing when limits are reached.

Yes, edge storage at Cloudflare KV stores user preferences and configuration data across the global network for instant retrieval. Metadata storage and list operations let you organize and retrieve related data efficiently, enabling personalization and feature flags without database roundtrips.

Pagination and bulk operations retrieve multiple keys efficiently from distributed storage. This Skill provides list, bulk read, and getWithMetadata methods to fetch related data across the edge network, reducing API calls and enabling efficient data synchronization patterns.

Stale-while-revalidate patterns serve cached data while refreshing it in the background. This Skill automates the pattern by storing responses with TTL expiration and edge caching, letting you serve stale content instantly and update asynchronously without blocking the user.

Yes, Wrangler is the required CLI tool to deploy and manage Cloudflare Workers and KV namespaces. This Skill uses Wrangler for configuration, local development, and production deployment of key-value storage to the edge.