In iotdb I currently see no way to consume mqtt messages from out of the box without running the moquette broker.
That's because the functionality of consuming the incoming messages is patched intro the server part of that. I personally have no objections to having an optional mqtt broker embedded, which users can activate if they don't have any other. But I would prefer, if the ingest would be done by a standard mqtt client instead of the way we are doing it right now. The main reason is: mqtt isn't built for this setup with multiple brokers (that don't form a cluster) But I see benefit of embedding bifromq instead of moquette, as that can also operate as an mqtt cluster if more than one datanode is used. Chris Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> ________________________________ From: Yuan Tian <[email protected]> Sent: Thursday, January 29, 2026 1:35:57 PM To: [email protected] <[email protected]> Subject: Re: [D] BifroMQ and MQTT ingestion for IoTDB Hi Yonny, I’ve spent the last couple of days studying the *BifroMQ* documentation. It’s a fascinating project with significant innovations compared to traditional MQTT servers. However, due to its unique architecture, other MQTT products can easily integrate downstream *sink components* (such as writing messages into *IoTDB*) via plugins. For downstream products like IoTDB, we only need to provide an official plugin; users can then simply load it into the broker with some configurations to enable data ingestion. This is incredibly convenient for users. I’m wondering if BifroMQ has any similar plans or alternative strategies in this regard? Best regards, ---------------------- Yuan Tian On Thu, Jan 29, 2026 at 8:28 PM Yonny Hao <[email protected]> wrote: > Hi all, > > Thanks Chris for introducing BifroMQ to the IoTDB community — just wanted > to jump in and say hi. > I’m Yonny, the original author of BifroMQ and currently one of the > maintainers. > > We’ve just released our first Apache Incubator version recently, and the > website has been updated with more details reflecting the latest progress > and design direction: > https://bifromq.apache.org/ > > I’d be very happy to explore possible ways the two projects could work > together, especially around MQTT ingestion at different scales. > > Although BifroMQ is primarily designed as a multi-tenant, distributed MQTT > broker for large-scale deployments, it can also run perfectly fine as a > single-tenant, single-node broker. Users can start simple, and later scale > out to a clustered or multi-tenant setup if and when needed — the > deployment model is quite flexible. > > Looking forward to the synergy and learning more about the IoTDB side as > well 🙂 > > Best, > -- > Yonny(Yu) Hao >
