Node.js - queue.dequeue()
Dequeue messages.
import { queue } from '@nitric/sdk'
const batchQueue = queue('batch').for('dequeue')
const tasks = await batchQueue.dequeue()
await Promise.all(
tasks.map((task) => {
// Work on a task...
// Complete the task
return task.complete()
})
)
Parameters
- Name
depth
- Optional
- Optional
- Type
- number
- Description
The maximum number of messages to dequeue. Defaults to 1.
Notes
Completing dequeued items
Since the process is asynchronous the queue doesn't know when a message has been processed. This ensures failed services/containers don't result in lost message, since messages are not removed from a queue when they're dequeued.
Instead, messages are hidden and requesters are granted a temporary lease for each message they request.
When processing is complete, the requester must tell the queue the task was completed successfully, which will remove it from the queue and stop it being reprocessed.
Failing to complete a dequeued message before the lease expires will result in it being re-queued.
To notify the queue that a message was completed call the complete()
method on the dequeued message reference.
Dequeue depth
When calling dequeue()
a depth parameter can be provided, e.g. dequeue(5)
. This will attempt to dequeue up to 5 messages from the queue.
However, if the queue is empty or less than 5 messages are available on the queue, then the maximum that are currently available will be returned.
This means calls to dequeue will return between 0 and depth tasks.
Examples
Dequeue and complete messages
import { queue } from '@nitric/sdk'
const batchQueue = queue('batch').for('dequeue')
const tasks = await batchQueue.dequeue(10)
await Promise.all(
tasks.map((task) => {
// Work on a task...
// Complete the task
return task.complete()
})
)