A new experimental feature has landed in MonsterMQ: It is acting now as a Kafka Broker, so a Kafka Client can subscribe (and publish, if allowed) to streams. Streams are mapped to MQTT topics. So MQTT topic value changes are going into those streams.
Before anyone asks: No, this is not a replacement for Apache Kafka. 🙂
The queueing is currently backed by databases such as PostgreSQL, MongoDB, and SQLite, so it won’t compete with Kafka in terms of throughput and scalability.
But for many smaller and medium-sized use cases, it brings streaming concepts directly into the broker:
- 🔹 MQTT and Kafka-style messaging in one server
- 🔹 Persistent queues stored in a database
- 🔹 Simple deployment without additional infrastructure
- 🔹 Easy integration with the existing MonsterMQ ecosystem
As always, this is a first draft – not yet in the version or docker image!
Feedback is welcome!
