Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Node-RED: Now With AMPQ 1.0 Support With the RHEA Nodes Library

DZone's Guide to

Node-RED: Now With AMPQ 1.0 Support With the RHEA Nodes Library

A brand new messaging and IoT library for providing AMQP 1.0 protocol support on Node-RED has just been released. Check out the features and go get it.

· IoT Zone
Free Resource

Discover why Bluetooth mesh is the next evolution of IoT solutions. Download the mesh overview.

The first version of a new messaging and IoT library for providing AMQP 1.0 protocol support on Node-RED — a tool for wiring Internet of Things — has just been released.

This library is based on the official JavaScript RHEA library, which provides AMQP 1.0 support for Node.js applications (developed by one of my best colleagues in Red Hat, Gordon Sim).

Up to now, the available nodes are:

  • Sender: for sending messages to an AMQP address.
  • Receiver: for receiving messages from an AMQP address.
  • Requester: for executing a request to an AMQP address and waiting for a response on the address specified in the “reply-to” field.
  • Responder: for receiving a request on an AMQP address and sending the response on the address specified in the “reply-to” field.

Of course, it’s open source (available on GitHub) with a "getting started" guide and documentation available on the related Wiki.

amqp_nodes

I published it on NPM (Node-RED is completely based on Node.js) at following link but you can find it even on the official Node-Red website in the flows section (searching for “amqp,” for example).

Enjoy AMQP messaging and IoT with Node-RED flow programming!

Take a deep dive into Bluetooth mesh. Read the tech overview and discover new IoT innovations.

Topics:
messaging ,node-red ,iot ,amqp

Published at DZone with permission of Paolo Patierno, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}