Skip to content

Releases: dadi/queue

v2.2.3

Choose a tag to compare

@jimlambie jimlambie released this 06 Jul 00:05
4f505a0

2.2.3 (2018-07-06)

Bug Fixes

  • .snyk & package.json to reduce vulnerabilities (96cfe94)

v2.2.2

Choose a tag to compare

@jimlambie jimlambie released this 06 Apr 11:59
08bbba8

2.2.2 (2018-04-06)

Bug Fixes

  • upgrade package lock to get logger latest (8247191)

v2.2.1

Choose a tag to compare

@jimlambie jimlambie released this 13 Mar 13:42
6fdc26c

2.2.1 (2018-03-13)

Bug Fixes

  • include mock-require (077b969)
  • pass correct config options to broker queue init (c1e9562)

Version 2.2.0

Choose a tag to compare

@adamkdean adamkdean released this 02 Mar 13:58

Changes

  • [5544b1] feat: initialize queue with queue name + options
  • [509492] feat: allow any string for env config field

Version 2.1.1

Choose a tag to compare

@jimlambie jimlambie released this 01 Mar 12:09

Changed

#11: Removes conf.validate() from the config loader so that custom values can be added to configuration files, and removes IP address validation from the queue.host configuration variable so that hostnames can be used.

Version 2.1.0

Choose a tag to compare

@jimlambie jimlambie released this 27 Oct 15:21

Features

  • unpack encapsulated base64 message data (706544e)

With queue-wrapper v1.1.0 and Queue v2.1.0 you can now send objects to a queue instead of just strings. Objects sent to the queue via queue-wrapper v1.1.0 send(address, object, callback) method are serialized if applicable, and then base64 encoded. This version of Queue supports unpacking these messages, decoding them, and if application, turning them from serialized JSON back into objects.

Version 2.0.0

Choose a tag to compare

@jimlambie jimlambie released this 25 Oct 16:51

Queue Throttling

Queue Version 2.0.0 introduces the ability to control how many messages are processed in a defined timespan. This can be useful if a consumer (worker) uses external APIs which are rate limited, for example.

Queue throttling gives:

  • the ability to set a default rate limit for the queue
  • the ability to set message specific rate limits

This version introduces a breaking change, in that the previous configuration for throttling the number of concurrent workers has been abstracted from broker.throttle to broker.throttle.workers.

See the README for updated configuration documentation.

Here is an example:

"throttle": {
  "workers": 5,
  "queue": {
    "unit": "second",
    "value": 1
  },
  "messages": [
    {
      "name": "ten-per-second",
      "regex": "^tps-.*$",  // messages starting with "tps-"
      "regexOpts": "i",
      "unit": "second",
      "value": 10
    },
    {
      "name": "one-per-minute",
      "regex": "^opm-.*$",  // messages starting with "opm-"
      "regexOpts": "i",
      "unit": "minute",
      "value": 1,
      "discard": true
    }
  ]
}

v1.1.1

Choose a tag to compare

@jimlambie jimlambie released this 07 Jun 13:08

<a name"1.1.1">

1.1.1 (2017-06-07)

Bug Fixes

  • ensure semantic release script is called (76db521b)

v1.1.0

Choose a tag to compare

@jimlambie jimlambie released this 07 Jun 12:59

<a name"1.1.0">

1.1.0 (2017-06-07)

Bug Fixes

  • add automatic folder creation (adbf068a)

Features

  • improve testability, and test coverage (a2bfe3cf)