dlandiak

9 ms·

1.
by dlandiak 7mo ago
Hi HN! I'm Dima from the ThingsBoard team — the company behind the open-source IoT platform and TBMQ, our MQTT broker built on top of Apache Kafka. Most MQTT brokers hit a ceiling when you need to scale horizontally or survive node fai
2.
Show HN: TBMQ – Live demo of a high-performance MQTT broker built on Kafka(demo.tbmq.io)
3 points by dlandiak 7mo ago|1 comments
3.
by dlandiak 1y ago
Yes, TBMQ currently uses Redis, but as a fully open-source broker that prioritizes open-source technologies, we’re following the community shift to Valkey and plan to support it in the next release.
4.
by dlandiak 1y ago
TBMQ 2.1 introduces native HTTP, MQTT, and Kafka integrations—plus an official Helm chart to make deploying your MQTT infrastructure easier than before.
5.
by dlandiak 1y ago
Our architecture introduces a new Integration Executor microservice, ensuring that outbound integrations have zero impact on the core MQTT broker’s performance.
6.
TBMQ 2.1 levels up your MQTT stack with embedded integrations and Helm support(thingsboard.io)
4 points by dlandiak 1y ago|6 comments
7.
Open-source MQTT broker shows market-leading performance(thingsboard.io)
5 points by dlandiak 2y ago|0 comments
8.
by dlandiak 3y ago
thank you, my friend :)
9.
by dlandiak 3y ago
As for me, TBMQ proposes the same reasons to use it as ActiveMQ Artemis. ActiveMQ Artemis seems to be a great platform that states about its high performance, clustering support, and data persistence. We believe TBMQ offers the same advant
10.
by dlandiak 3y ago
I would recommend reviewing the following article: https://bloomberg.github.io/blazingmq/docs/introduction/comp... Key points can be found there and everyone will choose their own priorities. For us these are
11.
by dlandiak 3y ago
RabbitMQ with the MQTT plugin is actually a good choice for many scenarios, especially when you need a messaging system that supports the MQTT protocol alongside other messaging protocols like AMQP. However, as they themselves say, There ar
12.
by dlandiak 3y ago
As far as I know, it is a lightweight MQTT broker designed to take good advantage of multi-CPU environments. We provide cluster support out of the box and are designed to support and work great for various setups, from small-scale to enterp
13.
by dlandiak 3y ago
We aim to be no worse than Emqx in this regard :) Planning to add auth modules support in the near future.
14.
by dlandiak 3y ago
Right, we are not stating anything without proving it in the first place. You can find another test here: https://thingsboard.io/docs/mqtt-broker/reference/3m-through...
15.
by dlandiak 3y ago
We are not very familiar with NATS, does it support the whole functionality the MQTT broker should support? In addition, as it is not Java, but we are working with it, it could not be our solution.
16.
by dlandiak 3y ago
We do not agree, but everyone has an opinion we should respect :)
17.
by dlandiak 3y ago
Exactly, you described it well. I have answered above for the reasons why HiveMQ was not the final choice.
18.
by dlandiak 3y ago
You are correct. TBMQ is based on Spring Boot. We use Netty ( https://netty.io/ ) as the source of the MQTT communication, and we build the MQTT features the MQTT broker should support ourselves on top of that. Kafka is use