nodes topic exchanges. Each node can create one queue and access to this queue is controlled by who have write access to this node. Queues have a random number appended to them so that they will be unique per replica instance. They can all listen on the same topic and act as workers.
Set up a worker like this:
register_queue(execution_context, ...) can take the following named parameters:
| Name | Type | Description |
|---|---|---|
| name | string | The name of the queue. Usually not something you change because it is tied to how the application autenticates using node level privielges. |
| topic | string | The topic to bind to. |
| durable | boolean | Will the queue survive a broker restart. |
| exclusive | boolean | Used by only one connection and the queue will be deleted when that connection closes |
| auto_delete | boolean | Queue that has had at least one consumer is deleted when last consumer unsubscribes |
| message_ttl | int | How long a messages can live if no consumer requests it. |
| max_length | int | Max length of a messages |
