This lesson's interactive features are locked, please to keep using them

MQTT and STOMP

We will be using RabbitMQ and AMQP in this course, but AMQP is not the only protocol for message brokers. Two other popular protocols are MQTT and STOMP.

MQTT is designed for small IoT devices and as such is optimized to be lightweight and energy efficient.
STOMP is designed for web applications and is designed to be simple and easy to use.
AMQP is a sophisticated, feature-rich protocol that's great for complex routing, filtering, and delivery requirements.

Assignment

While we'll be using AMQP during the rest of this course, let's configure our RabbitMQ instance to support STOMP as well, just for fun. We'll need to create our own Dockerfile that installs the RabbitMQ STOMP plugin.

Create a file called Dockerfile with the following contents:

FROM rabbitmq:3.13-management
RUN rabbitmq-plugins enable --offline rabbitmq_stomp

build the image, and name it rabbitmq-stomp:
```
docker build -t rabbitmq-stomp .
```
If you have rabbit running, use ./rabbit.sh stop to stop it.
Remove the stopped container so its name can be reused:
```
docker rm peril_rabbitmq
```

Start one container with your image and all three ports exposed:

docker run -d --name peril_rabbitmq -p 5672:5672 -p 15672:15672 -p 61613:61613 rabbitmq-stomp

Once it's running, test port 61613 with NetCat to make sure that it's open and that RabbitMQ is running the STOMP plugin:

nc -vz localhost 61613

You should get a "connection succeeded" message if all is well.

Run and submit the CLI tests.

Shutdown the Docker container when you're done.