ارتباطات الخدمات والتكاملات

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.

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.

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.

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:

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:

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.

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.

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:

Choose the best answer.

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!