Edge Computing with Cloudflare Workers & Deno · Leçon

Files d’attente et tâches asynchrones

Exploitez Cloudflare Queues pour gérer les tâches asynchrones et le traitement en arrière-plan à grande échelle.

Files d’attente et tâches asynchrones est une leçon Edge Computing with Cloudflare Workers & Deno gratuite sur CoddyKit. Ceci est la leçon 2 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Edge Computing with Cloudflare Workers & Deno, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Edge Computing with Cloudflare Workers & Deno comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

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!

Questions Fréquemment Posées

La leçon « Files d’attente et tâches asynchrones » est-elle gratuite ?

Oui — le texte complet de « Files d’attente et tâches asynchrones » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Edge Computing with Cloudflare Workers & Deno, passe à CoddyKit PRO. Le cours Edge Computing with Cloudflare Workers & Deno comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Files d’attente et tâches asynchrones » ?

Exploitez Cloudflare Queues pour gérer les tâches asynchrones et le traitement en arrière-plan à grande échelle. Tu pratiques Edge Computing with Cloudflare Workers & Deno avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer Edge Computing with Cloudflare Workers & Deno ?

Aucune expérience préalable n'est requise. Edge Computing with Cloudflare Workers & Deno sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 2 sur 4.

Combien de temps prend la leçon « Files d’attente et tâches asynchrones » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon Edge Computing with Cloudflare Workers & Deno ?

Oui. Chaque leçon Edge Computing with Cloudflare Workers & Deno inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

← Retour à Edge Computing with Cloudflare Workers & Deno