rhea-promise

What is rhea-promise?

The rhea-promise npm package is a promise-based wrapper around the rhea library, which is an AMQP 1.0 client for Node.js. It simplifies the process of working with AMQP 1.0 by providing a more modern, promise-based API.

What are rhea-promise's main functionalities?

Sending Messages

This feature allows you to send messages to an AMQP 1.0 broker. The code sample demonstrates how to establish a connection, create a sender, send a message, and then close the sender and connection.

const { Connection, Sender } = require('rhea-promise');

async function sendMessage() {
  const connection = new Connection({ host: 'localhost', port: 5672 });
  await connection.open();
  const sender = await connection.createSender({ target: { address: 'queue' } });
  await sender.send({ body: 'Hello, World!' });
  await sender.close();
  await connection.close();
}

sendMessage().catch(console.error);

Receiving Messages

This feature allows you to receive messages from an AMQP 1.0 broker. The code sample demonstrates how to establish a connection, create a receiver, and handle incoming messages.

const { Connection, Receiver } = require('rhea-promise');

async function receiveMessages() {
  const connection = new Connection({ host: 'localhost', port: 5672 });
  await connection.open();
  const receiver = await connection.createReceiver({ source: { address: 'queue' } });
  receiver.on('message', (context) => {
    console.log('Received message:', context.message.body);
  });
}

receiveMessages().catch(console.error);

Request-Response Pattern

This feature allows you to implement a request-response pattern using AMQP 1.0. The code sample demonstrates how to send a request message and handle the response.

const { Connection, Sender, Receiver } = require('rhea-promise');

async function requestResponse() {
  const connection = new Connection({ host: 'localhost', port: 5672 });
  await connection.open();
  const sender = await connection.createSender({ target: { address: 'request_queue' } });
  const receiver = await connection.createReceiver({ source: { address: 'response_queue' } });

  receiver.on('message', (context) => {
    console.log('Received response:', context.message.body);
  });

  await sender.send({ body: 'Request message' });
}

requestResponse().catch(console.error);

Other packages similar to rhea-promise

amqp10

The amqp10 package is another AMQP 1.0 client for Node.js. It provides a similar set of functionalities as rhea-promise but uses a callback-based API instead of promises. This can make the code less readable and harder to manage compared to the promise-based approach of rhea-promise.

amqplib

The amqplib package is an AMQP 0.9.1 client for Node.js. While it does not support AMQP 1.0, it is widely used for RabbitMQ, which uses AMQP 0.9.1. It provides a callback-based API and is well-documented, making it a good choice for projects that do not require AMQP 1.0.

rhea

The rhea package is the underlying library that rhea-promise wraps around. It provides a more low-level, event-driven API for working with AMQP 1.0. While it offers more control and flexibility, it can be more complex to use compared to the promise-based API of rhea-promise.

README

rhea-promise

A Promisified layer over rhea AMQP client.

Pre-requisite

• Node.js version: 6.x or higher.
• We would still encourage you to install the latest available LTS version at any given time from https://nodejs.org. It is a good practice to always install the latest available LTS version of node.js.
• Installing node.js on Windows or macOS is very simple with available installers on the node.js website. If you are using a linux based OS, then you can find easy to follow, one step installation instructions over here.

Installation

npm install rhea-promise

Debug logs

You can set the following environment variable to get the debug logs.

• Getting debug logs from the library

export DEBUG=rhea*

• If you are not interested in viewing the message transformation (which consumes lot of console/disk space) then you can set the DEBUG environment variable as follows:

export DEBUG=rhea*,-rhea:raw,-rhea:message

Logging to a file

• Set the DEBUG environment variable as shown above and then run your test script as follows:
  • Logging statements from you test script go to out.log and logging statement from the sdk go to debug.log.

    node your-test-script.js > out.log 2>debug.log
    

  • Logging statements from your test script and the sdk go to the same file out.log by redirecting stderr to stdout (&1), and then redirect stdout to a file:

    node your-test-script.js >out.log 2>&1
    

  • Logging statements from your test script and the sdk go to the same file out.log.

      node your-test-script.js &> out.log
    

Notable differences between rhea and rhea-promise

Error propogation to the parent entity

• In AMQP, for two peers to communicate successfully, different entities (Container, Connection, Session, Link) need to be created. There is a relationship between those entities.
  • 1 Container can have 1..* Connections.
  • 1 Connection can have 1..* Sessions.
  • 1 Session can have 1..* Links.
  • A Link can have the role of Receiver or Sender.
• Each entity (connection, session, link) maintains its own state to let other entities know about what it is doing. Thus,
  • if the connection goes down then, everything on the connection - sessions, links are down.
  • if a session goes down then, all the the links on that session are down.
• When an entity goes down rhea emits *_error and *_close events, where * can be "sender", "receiver", "session", "connection". If event listeners for the aforementioned events are not added at the appropriate level, then rhea propogates those events to its parent entity. If they are not handled at the Container level (uber parent), then they are transformed into an error event. This would cause your application to crash if there is no listener added for the error event.
• In rhea-promise, the library creates, equivalent objects Connection, Session, Sender, Receiver and wraps objects from rhea within them. It adds event listeners to all the possible events that can occur at any level and re-emits those events with the same arguments as one would expect from rhea. This makes it easy for consumers of rhea-promise to use the EventEmitter pattern. Users can efficiently use different event emitter methods like .once(), .on(), .prependListeners(), etc. Since rhea-promise add those event listeners on rhea objects, the errors will never be propogated to the parent entity. This can be good as well as bad depending on what you do.
  • Good - *_error events and *_close events emitted on an entity will not be propogated to it's parent. Thus ensuring that errors are handled at the right level.
  • Bad - If you do not add listeners for *_error and *_close events at the right level, then you will never know why an entity shutdown.

We believe our design enforces good practices to be followed while using the event emitter pattern.

Examples

Please take a look at the sample.env file for examples on how to provide the values for different parameters like host, username, password, port, senderAddress, receiverAddress, etc.

Sending a message.

• Running the example from terminal: > ts-node ./examples/send.ts.

NOTE: If you are running the sample with .env config file, then please run the sample from the directory that contains .env config file.

import {
  Connection, Sender, EventContext, Message, ConnectionOptions, Delivery, SenderOptions
} from "rhea-promise";
import * as dotenv from "dotenv"; // Optional for loading environment configuration from a .env (config) file
dotenv.config();

const host = process.env.AMQP_HOST || "host";
const username = process.env.AMQP_USERNAME || "sharedAccessKeyName";
const password = process.env.AMQP_PASSWORD || "sharedAccessKeyValue";
const port = parseInt(process.env.AMQP_PORT || "5671");
const senderAddress = process.env.SENDER_ADDRESS || "address";

async function main(): Promise<void> {
  const connectionOptions: ConnectionOptions = {
    transport: "tls",
    host: host,
    hostname: host,
    username: username,
    password: password,
    port: port,
    reconnect: false
  };
  const connection: Connection = new Connection(connectionOptions);
  const senderName = "sender-1";
  const senderOptions: SenderOptions = {
    name: senderName,
    target: {
      address: senderAddress
    },
    onError: (context: EventContext) => {
      const senderError = context.sender && context.sender.error;
      if (senderError) {
        console.log(">>>>> [%s] An error occurred for sender '%s': %O.",
          connection.id, senderName, senderError);
      }
    },
    onSessionError: (context: EventContext) => {
      const sessionError = context.session && context.session.error;
      if (sessionError) {
        console.log(">>>>> [%s] An error occurred for session of sender '%s': %O.",
          connection.id, senderName, sessionError);
      }
    }
  };

  await connection.open();
  const sender: Sender = await connection.createSender(senderOptions);
  const message: Message = {
    body: "Hello World!!",
    message_id: "12343434343434"
  };

  const delivery: Delivery = await sender.send(message);
  console.log(">>>>>[%s] Delivery id: ", connection.id, delivery.id);

  await sender.close();
  await connection.close();
}

main().catch((err) => console.log(err));

Receiving a message

• Running the example from terminal: > ts-node ./examples/receive.ts.

NOTE: If you are running the sample with .env config file, then please run the sample from the directory that contains .env config file.

import {
  Connection, Receiver, EventContext, ConnectionOptions, ReceiverOptions, delay, ReceiverEvents
} from "rhea-promise";
import * as dotenv from "dotenv"; // Optional for loading environment configuration from a .env (config) file
dotenv.config();

const host = process.env.AMQP_HOST || "host";
const username = process.env.AMQP_USERNAME || "sharedAccessKeyName";
const password = process.env.AMQP_PASSWORD || "sharedAccessKeyValue";
const port = parseInt(process.env.AMQP_PORT || "5671");
const receiverAddress = process.env.RECEIVER_ADDRESS || "address";

async function main(): Promise<void> {
  const connectionOptions: ConnectionOptions = {
    transport: "tls",
    host: host,
    hostname: host,
    username: username,
    password: password,
    port: port,
    reconnect: false
  };
  const connection: Connection = new Connection(connectionOptions);
  const receiverName = "receiver-1";
  const receiverOptions: ReceiverOptions = {
    name: receiverName,
    source: {
      address: receiverAddress
    },
    onSessionError: (context: EventContext) => {
      const sessionError = context.session && context.session.error;
      if (sessionError) {
        console.log(">>>>> [%s] An error occurred for session of receiver '%s': %O.",
          connection.id, receiverName, sessionError);
      }
    }
  };

  await connection.open();
  const receiver: Receiver = await connection.createReceiver(receiverOptions);
  receiver.on(ReceiverEvents.message, (context: EventContext) => {
    console.log("Received message: %O", context.message);
  });
  receiver.on(ReceiverEvents.receiverError, (context: EventContext) => {
    const receiverError = context.receiver && context.receiver.error;
    if (receiverError) {
      console.log(">>>>> [%s] An error occurred for receiver '%s': %O.",
        connection.id, receiverName, receiverError);
    }
  });
  // sleeping for 2 mins to let the receiver receive messages and then closing it.
  await delay(120000);
  await receiver.close();
  await connection.close();
}

main().catch((err) => console.log(err));

Building the library

• Clone the repo

git clone https://github.com/amqp/rhea-promise.git

• Install typescript, ts-node globally

npm i -g typescript
npm i -g ts-node

• NPM install from the root of the package

npm i

• Build the project

npm run build

Changelog

0.1.3 - 2018-09-25

• Transform relevant objects in rhea EventContext to rhea-promise objects.
• Ensure that container.createConnection() creates a connection on that container and not on the default container.