Both hands agree “refactor IoTDB to be able to use any MQTT broker” Xuan Wang
Best regards, Xuan Wang ________________________________ From: Christofer Dutz <christofer.d...@c-ware.de> Sent: Monday, April 29, 2024 8:00:52 PM To: dev@iotdb.apache.org <dev@iotdb.apache.org> Subject: [DISCUSS] Refactor the MQTT subsystem to work with external MQTT Brokers? Hi all, currently a lot of the plans we have for 2024 (at least my plans) involve MQTT as one form of transport for data into IoTDB. Unfortunately, currently all of IoTDBs MQTT support is built around the built-in Moquette MQTT broker. However, I think it’s totally out of the question, that any larger company would agree on using this broker as their communication back-bone. Therefore, I would propose to refactor IoTDB to be able to use any MQTT broker as client but to keep Moquette in there, if a user doesn’t have an MQTT broker available. The main change that we would need, would be to refactor the code that currently integrates into Moquette for processing messages and to rewrite this to use a normal MQTT client library. What do you others think about this? Chris
