Skip to content

bbc/sqs-consumer

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

40 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

sqs-consumer

Build Status Code Climate Test Coverage

Build SQS-based applications without the boilerplate. Just define a function that receives an SQS message and call a callback when the message has been processed.

Installation

npm install sqs-consumer

Usage

var Consumer = require('sqs-consumer');

var app = Consumer.create({
  queueUrl: 'https://sqs.eu-west-1.amazonaws.com/account-id/queue-name',
  handleMessage: function (message, done) {
    // do some work with `message`
    done();
  }
});

app.on('error', function (err) {
  console.log(err.message);
});

app.start();
  • The queue is polled continuously for messages using long polling.
  • Messages are deleted from the queue once done() is called.
  • Calling done(err) with an error object will cause the message to be left on the queue. An SQS redrive policy can be used to move messages that cannot be processed to a dead letter queue.
  • By default messages are processed one at a time – a new message won't be received until the first one has been processed. To process messages in parallel, use the batchSize option detailed below.

API

Consumer.create(options)

Creates a new SQS consumer.

Options

  • queueUrl - String - The SQS queue URL
  • region - String - The AWS region (default eu-west-1)
  • handleMessage - Function - A function to be called whenever a message is received. Receives an SQS message object as its first argument and a function to call when the message has been handled as its second argument (i.e. handleMessage(message, done)).
  • messageAttributeNames - Array - List of message attributes to retrieve (i.e. ['name', 'address']).
  • batchSize - Number - The number of messages to request from SQS when polling (default 1). This cannot be higher than the AWS limit of 10.
  • sqs - Object - An optional AWS SQS object to use if you need to configure the client manually

consumer.start()

Start polling the queue for messages.

consumer.stop()

Stop polling the queue for messages.

Events

Each consumer is an EventEmitter and emits the following events:

Event Params Description
error err Fired when an error occurs interacting with the queue or processing the message.
message_received message Fired when a message is received.
message_processed message Fired when a message is successfully processed and removed from the queue.