Integrating Deno with Edge Storage
Develop Deno functions that interact with Cloudflare KV and Durable Objects for data management.
Deno & Edge Storage Integration
Welcome! In previous lessons, we learned about Cloudflare KV and Durable Objects for storing data at the edge. Now, let's explore how Deno applications can interact with these powerful edge storage solutions.
Since Deno typically runs outside the Cloudflare Workers environment, we'll focus on how Deno can act as a client, communicating with Cloudflare Workers that then manage interactions with KV and Durable Objects.
Deno's Role: The Proxy Pattern
Deno applications, whether running locally or deployed on platforms like Deno Deploy, don't directly access Cloudflare's KV or Durable Objects.
Instead, Deno acts as a client, making standard HTTP requests to a Cloudflare Worker. This Worker then serves as a proxy, handling the actual interactions with KV or Durable Objects on the Cloudflare edge network.
- Deno App: Sends HTTP requests (e.g., GET, POST).
- Cloudflare Worker: Receives requests, accesses KV/DO, and sends responses.
All lessons in this course
- Cloudflare KV Store
- Durable Objects Explained
- Integrating Deno with Edge Storage
- Querying with D1 SQL at the Edge