Rate Limiting & Idempotency using Push Based consumers

Original message was deleted

rodrigo•3/20/25, 7:05 PM

Hello Cloudflare team!

I’m exploring Queues for the first time.

I had a question regarding best practices and recommendations.

I’m using Queues primarily to rate limit our usage of a third-party API during peak times (~100 QPS). Since messages must not be consumed more than once, I figured setting no concurrency with a batch size of 100 and calling .ack() on success would suffice.

I considered pull-based consumers, but since this API is not frequently hit, I opted for a push-based approach with the following setup:

function consumeMessage(batch) {
  startTime = now();
  for (const message of batch) {
    try {
      // Call third-party API
      message.ack();
    } catch {
      message.retry();
    }
  }
  elapsedTime = now() - startTime;
  sleep(1 second - elapsedTime); // Ensures at least 1 second per batch
}

function consumeMessage(batch) {
  startTime = now();
  for (const message of batch) {
    try {
      // Call third-party API
      message.ack();
    } catch {
      message.retry();
    }
  }
  elapsedTime = now() - startTime;
  sleep(1 second - elapsedTime); // Ensures at least 1 second per batch
}

Am I missing anything? Is there a better way to enforce the rate limit while maintaining idempotency?

Thanks in advance!

Rate Limiting & Idempotency using Push Based consumers

Similar Threads

Similar Threads

Similar Threads