mq-connection

Cached, idempotent connections to an AMQP/RabbitMQ server.

---

RabbitMQ connections are expensive to create and destroy. You want avoid having too many open connections, in contrast to channels which you can (and should) have many of over a single open channel (ref).

This module allows you to work with a single cached connection for each server URL. This is useful when you are developing different modules that connect to RabbitMQ, and don't wish to explicitly pass connections around between API's.

See also:

• mq-pubsub
• mq-pushworker
• amqplib

Installation

npm install --save mq-connection

Usage

import connect from "mq-connection";
 
connect("amqp://rabbitmq")
  .then(connection => {
    // An `amqplib` connection object is returned.
  });
 
connect("amqp://rabbitmq")
  .then(connection => {
    // This `connection` is the same (cached) connection that was returned above.
  });
 

The amqp connection that is returned has a modified close() method that returns a promise, allowing you to determine exactly when the connection has successfully closed.

connection.close()
  .then(result => {
    // The connection is now closed.
  });

Once closed the connection is removed from the cache.

Fakes

You can easily return fake connections for the purposes of testing using the fake() method:

import connect from "mq-connection";
connect.fake();
 
connect("amqp://whatever")
  .then(connection => {
    // This is a {FakeConnection}.
  });
 

To restore the module to make real connections use the 'real()' method:

import connect from "mq-connection";
connect.fake(); // Makes fake connections.
...
connect.real(); // Back to making real connections now.

The fake API's are being fleshed out as needed. If a method that you need is not there feel free to add it and submit a pull-request.

Tests

npm test

---

License: MIT