Edge Computing with Cloudflare Workers & Deno · 课时

服务绑定与集成

使用服务绑定将 Workers 连接到其他 Cloudflare 服务和外部 API

服务绑定与集成 是 CoddyKit 上的免费 Edge Computing with Cloudflare Workers & Deno 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Edge Computing with Cloudflare Workers & Deno 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Edge Computing with Cloudflare Workers & Deno 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Intro to Service Bindings

Welcome to Service Bindings! In this lesson, you'll learn how Cloudflare Workers can communicate with each other and other Cloudflare services directly.

Think of Service Bindings as secure, internal connections that unlock powerful modularity for your edge applications.

Why Use Service Bindings?

Service Bindings offer several key advantages:

Modularity: Break down complex Workers into smaller, reusable components.
Performance: Direct internal communication is faster than public HTTP requests.
Security: Keep internal API calls off the public internet.
Abstraction: Treat other Workers or services like local modules.

Worker-to-Worker Communication

One of the most common uses for Service Bindings is allowing one Worker to invoke another. This is perfect for creating microservices at the edge.

You can call a 'target' Worker from an 'invoking' Worker, passing requests and receiving responses as if they were part of the same application.

Code: The Target Worker

First, let's create a simple 'target' Worker. This Worker will respond with a specific message when called.

Save this as target-worker/src/index.js:

export default {
  async fetch(request, env, ctx) {
    return new Response("Hello from the Target Worker!", {
      status: 200,
      headers: { 'Content-Type': 'text/plain' }
    });
  },
};

Code: The Invoking Worker

Now, let's create an 'invoking' Worker that uses a binding to call our 'target' Worker. Notice how env.TARGET_WORKER.fetch(request) is used.

Save this as invoking-worker/src/index.js:

export default {
  async fetch(request, env, ctx) {
    // 'TARGET_WORKER' is the binding name defined in wrangler.toml
    const response = await env.TARGET_WORKER.fetch(request);
    const text = await response.text();
    return new Response(`Invoker received: ${text}`, {
      status: 200,
      headers: { 'Content-Type': 'text/plain' }
    });
  },
};

Configuring Worker Bindings

To connect the 'invoking' Worker to the 'target' Worker, you need to add a service_binding entry in the wrangler.toml file of your invoking Worker.

This tells Cloudflare which Worker project to connect to and what name (e.g., TARGET_WORKER) to use in your code.

# In the invoking-worker's wrangler.toml
name = "invoking-worker"
main = "src/index.js"
compatibility_date = "2023-12-01"

[[service_bindings]]
name = "TARGET_WORKER"
service = "target-worker" # Name of the target Worker project

Make sure both Workers are deployed to Cloudflare.

Bindings to Cloudflare Services

Service Bindings aren't limited to Workers! You can also bind your Worker directly to other Cloudflare services like KV Namespaces, R2 buckets, D1 databases, and Durable Objects.

This provides your Worker with direct, secure, and performant access to these resources via the env object.

Code: KV Namespace Binding

Here's how you'd configure a binding to a KV Namespace in your wrangler.toml:

# In your Worker's wrangler.toml
name = "my-worker"
main = "src/index.js"
compatibility_date = "2023-12-01"

[[kv_namespaces]]
binding = "MY_KV" # The variable name in your Worker
id = "YOUR_KV_NAMESPACE_ID" # Replace with your actual KV ID

Then, access it in your Worker's code:

export default {
  async fetch(request, env, ctx) {
    // 'MY_KV' is the binding name from wrangler.toml
    await env.MY_KV.put("greeting", "Hello from KV!");
    const message = await env.MY_KV.get("greeting");
    return new Response(`KV says: ${message}`, {
      status: 200,
      headers: { 'Content-Type': 'text/plain' }
    });
  },
};

Test Your Knowledge!

Choose the best answer.

Recap: Bindings & Integrations

You've learned about Cloudflare Worker Service Bindings!

They provide a powerful way for Workers to communicate with other Workers or Cloudflare services directly.
Benefits include modularity, performance, and security.
You configure bindings in your wrangler.toml file.
They enable complex architectures where Workers act as building blocks.

Keep exploring how these bindings can simplify your edge development!

常见问题解答

「服务绑定与集成」课时是免费的吗？

是的 — 「服务绑定与集成」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Edge Computing with Cloudflare Workers & Deno 课程的其余内容，请升级到 CoddyKit PRO。 Edge Computing with Cloudflare Workers & Deno 课程共包含 4 节课。

「服务绑定与集成」这节课中我会学到什么？

使用服务绑定将 Workers 连接到其他 Cloudflare 服务和外部 API 你通过在浏览器中直接运行的动手代码来练习 Edge Computing with Cloudflare Workers & Deno，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Edge Computing with Cloudflare Workers & Deno 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Edge Computing with Cloudflare Workers & Deno 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「服务绑定与集成」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Edge Computing with Cloudflare Workers & Deno 课中编写并运行代码吗？

能。每节 Edge Computing with Cloudflare Workers & Deno 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Edge Computing with Cloudflare Workers & Deno