Edge Computing with Cloudflare Workers & Deno · 강의

대기열 및 비동기 작업

Cloudflare Queues를 활용하여 대규모 비동기 작업과 백그라운드 처리를 관리합니다.

대기열 및 비동기 작업은(는) CoddyKit의 무료 Edge Computing with Cloudflare Workers & Deno 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Edge Computing with Cloudflare Workers & Deno 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Edge Computing with Cloudflare Workers & Deno 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

Async Tasks at the Edge

At the edge, users expect lightning-fast responses. But not every task needs to happen instantly. Sometimes, you have operations that can run in the background, like sending emails, processing analytics, or generating reports.

These are called asynchronous tasks. They don't block the user's immediate request, allowing your Worker to respond quickly while the longer task completes separately.

Introducing Cloudflare Queues

Cloudflare Queues provide a robust way to manage these asynchronous tasks. They act as a buffer, allowing different parts of your application (often Cloudflare Workers) to communicate without needing to be directly available at the same time.

Think of it like a to-do list where one Worker adds tasks, and another Worker picks them up when it's ready.

Queue Fundamentals: P-C-M

Every message queue system, including Cloudflare Queues, revolves around three core concepts:

Producers: The entities that create and send messages to the queue. In our case, this will often be a Cloudflare Worker responding to an HTTP request.
Consumers: The entities that retrieve messages from the queue and process them. This is typically another Cloudflare Worker configured to listen to the queue.
Messages: The actual data or task instructions being passed through the queue.

Configuring Your First Queue

To use Cloudflare Queues, you first need to create a queue in your Cloudflare dashboard or via the Wrangler CLI. Once created, you bind it to a Worker, making it accessible through the Worker's env object.

This binding specifies the name your Worker will use to interact with the queue (e.g., env.MY_QUEUE).

Sending Messages to a Queue

A Worker acting as a Producer will send messages to a bound queue using the send() method. This method takes a JavaScript object as its argument, which will be serialized and stored in the queue.

The send() operation is asynchronous itself, but it ensures the message is enqueued quickly, allowing the producer Worker to complete its primary task without waiting for the message to be processed.

Worker Producing Messages

Here's an example of a Worker receiving an HTTP request and sending a simple message to a queue named MY_QUEUE. The user gets an immediate response.

export interface Env {
  MY_QUEUE: Queue;
}

export default {
  async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
    const url = new URL(request.url);
    if (url.pathname === '/send-task') {
      const message = {
        type: 'email_notification',
        userId: 'user123',
        subject: 'Welcome to CoddyKit!'
      };
      await env.MY_QUEUE.send(message);
      return new Response('Email task enqueued!', { status: 200 });
    }
    return new Response('Hello from Producer Worker!', { status: 200 });
  },
};

Processing Queue Messages

A Worker acting as a Consumer is configured with a special queue handler. This handler is invoked by Cloudflare when there are messages available in the bound queue. Messages are delivered in batches for efficiency.

Inside the queue handler, you iterate through the batch.messages array. For each message, you can access its body (the data sent by the producer) and perform the necessary background processing.

Worker Consuming Messages

This Worker is configured to listen to MY_QUEUE. It processes each message in the batch. If a message is processed successfully, message.ack() acknowledges it. If an error occurs, message.retry() sends it back to the queue for another attempt.

export interface Env {
  MY_QUEUE: Queue;
}

export default {
  async queue(batch: MessageBatch, env: Env): Promise<void> {
    for (const message of batch.messages) {
      try {
        const data = message.body as {
          type: string;
          userId: string;
          subject: string;
        };
        console.log(`Processing ${data.type} for ${data.userId}: ${data.subject}`);
        // Simulate sending an email or other background task
        await new Promise(resolve => setTimeout(resolve, 500));
        message.ack(); // Mark message as processed successfully
      } catch (error) {
        console.error(`Error processing message: ${error}`);
        message.retry(); // Re-queue for another attempt
      }
    }
  },
};

Why Use Edge Queues?

Cloudflare Queues offer several powerful benefits for edge applications:

Decoupling: Producers and consumers don't need to know about each other directly.
Reliability: Messages are persistent and can be retried automatically if processing fails.
Load Leveling: Queues absorb spikes in demand, preventing your backend services from being overwhelmed.
Scalability: Easily scale processing by adding more consumer Workers without affecting producers.
Asynchronous Processing: Crucial for keeping user-facing responses fast.

Practical Queue Use Cases

Queues are incredibly versatile. Here are some common scenarios where Cloudflare Queues shine:

Analytics & Logging: Collect and process user event data in the background.
Image/Video Processing: Trigger resizing or watermarking after an upload.
Notifications: Send emails, SMS, or push notifications without delaying the user.
Data Synchronization: Propagate changes to multiple downstream services asynchronously.
Batch Jobs: Schedule and execute periodic data transformations or cleanup tasks.

Queue Concepts Check

Consider a scenario where a Cloudflare Worker needs to initiate a background task (e.g., sending an email) without delaying the user's response. Which of the following statements about Cloudflare Queues are correct for this scenario?

Recap & Next Steps

You've now explored Cloudflare Queues, a powerful tool for managing asynchronous tasks at the edge. We covered the producer-consumer model, how to send and process messages, and the significant benefits queues bring, such as improved reliability, scalability, and faster user responses.

By decoupling tasks with queues, your edge applications can handle complex operations efficiently without compromising performance. Experiment with creating your own queues and Workers to build robust, asynchronous workflows!

자주 묻는 질문

“대기열 및 비동기 작업” 강의는 무료인가요?

네 — “대기열 및 비동기 작업” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Edge Computing with Cloudflare Workers & Deno 강의 전체를 잠금 해제할 수 있습니다. Edge Computing with Cloudflare Workers & Deno 강의에는 총 4개의 강의가 포함되어 있습니다.

“대기열 및 비동기 작업”에서 뭘 배우나요?

Cloudflare Queues를 활용하여 대규모 비동기 작업과 백그라운드 처리를 관리합니다. 브라우저에서 직접 실행하는 실습 코드로 Edge Computing with Cloudflare Workers & Deno을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Edge Computing with Cloudflare Workers & Deno을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Edge Computing with Cloudflare Workers & Deno은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.

“대기열 및 비동기 작업” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Edge Computing with Cloudflare Workers & Deno 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Edge Computing with Cloudflare Workers & Deno 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

← Edge Computing with Cloudflare Workers & Deno(으)로 돌아가기