Skip to content
Drizzle KV Cache

Introduction

Drizzle Cloudflare KV Cache Adapter — Cloudflare KV-backed query caching for Drizzle ORM

Available on npm as drizzle-cloudflare-kv-cache-adapter.

A Cloudflare KV-backed implementation of Drizzle ORM’s cache interface. It caches read-heavy Drizzle queries at the edge using the KV namespace you already have bound to your Worker.

Why

Section titled “Why”

Drizzle’s cache layer ships with a Redis/Upstash adapter out of the box. On Cloudflare Workers + D1 you usually don’t want to add a Redis dependency just to cache a few hot queries. KV is already there, globally replicated, and free-tier friendly — so use it.

When it fits

Section titled “When it fits”
  • Read-heavy queries that tolerate brief staleness (config, catalogs, public profiles).
  • Workers / D1 apps that want caching without new infrastructure.
  • Anything where a 60-second-or-more TTL is acceptable.

When it does not fit

Section titled “When it does not fit”
  • Read-after-write strong consistency. KV is eventually consistent.
  • Sub-60-second freshness. KV enforces a 60s minimum TTL.
  • Per-row caching with high write churn — invalidation is table-scoped.

Requirements

Section titled “Requirements”
  • drizzle-orm >= 0.44.0
  • A bound KVNamespace in your Worker (env.CACHE or similar).

Disclaimer

Section titled “Disclaimer”

This is an independent, community-maintained project. It is not affiliated with, endorsed by, or sponsored by Drizzle ORM or Cloudflare, Inc. “Drizzle”, “Cloudflare”, “Cloudflare Workers”, “Workers KV”, and “D1” are trademarks of their respective owners and are used here for identification purposes only.

This adapter exists because of an open upstream feature request — drizzle-team/drizzle-orm#5758, which asks for a first-party Cloudflare KV cache adapter in Drizzle ORM. At the time of writing that request is still open and Drizzle does not ship an official Cloudflare KV adapter. This package is an independent implementation of Drizzle’s public cache interface that fills the gap in the meantime; it is not the first-party adapter discussed in that issue. If an official adapter ever lands upstream, we’ll help users migrate to it.