The message broker should:
ActiveMQ seems the low risk, but others are compatible with protocols becoming more and more standard.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | dereckson | T580 Create a notification center, with a message broker | |||
| Resolved | dereckson | T583 Deploy a message broker like ActiveMQ on Dwellers |
Plugins exist for RabbitMQ:
Changelog doesn't show any compatibility with other brokers.
RabbitMQ has a STOMP adapter, see https://www.rabbitmq.com/stomp.html.
It also provides a MQTT adapter, where a less maintained plugin does exist.
Of course, Apache ActiveMQ and Apache Apollo speaks also STOMP and MQTT.
Let's go for a test drive of RabbitMQ.
DNS configuration
app2.nasqueron.org. 86400 IN A 212.129.32.223
app2.nasqueron.org. 86400 IN AAAA 2001:470:1f13:ce7:ca5:cade:fab:1e
white-rabbit.nasqueron.org. 86400 IN CNAME app2.nasqueron.org
Container launched on Dwellers for white-rabbit.nasqueron.org ActiveMQ broker, see P130.
We've redeployed RabbitMQ with more network ports open and STOMP / MQTT / management plugins enabled.
Our image has been published at rDRABBITMQ.
This works fine.