Re:Eclipse Mosquitto – An open source MQTT broker
by monkeyking135 on Sunday November 15, 2026 @02:11PM
(#50509714)
I’m confused why this post is on the front page of HN. This isn’t new and they haven’t done a new release or something. Mosquitto is good and used all over the place but not sure why this is being posted.
Re:Eclipse Mosquitto – An open source MQTT broker
by edukite on Sunday November 15, 2026 @02:23PM
(#50509820)
Exactly, I honestly checked link thinking there's v6 of mqtt protocol and I slept something and was confused. So I checked comments because maybe I'm to stupid but nope. There's literally nothing
Re:Eclipse Mosquitto – An open source MQTT broker
by gregsadetsky on Sunday November 15, 2026 @02:39PM
(#50509950)
I'm the OP - I just stumbled upon this project because I setup a self hosted MQTT server to read/write to/from a small PDU.
I hadn't heard of it, and thought to share it. I'm not sure why people are upvoting it - but it's not impossible that others are interested too in this topic..! Cheers
Re:Eclipse Mosquitto – An open source MQTT broker
by riedel on Sunday November 15, 2026 @02:51PM
(#50510056)
Maybe NanoMQ 0.25, Rabbitmq 4.4, EMQX 6.3 or VerneMQ 2.2 would have been a bit more newsworthy. Mosquito seems to the rather boring but but stable reference for MQTT for years now.
Re:Eclipse Mosquitto – An open source MQTT broker
by oulipo on Sunday November 15, 2026 @02:39PM
(#50509955)
Now the default seems to be EMQX, there's also a possible project to include MQTT5 compatibility in NATS (but they push back because they are selling this in their Entreprise version), what stack do people use here for MQTT?
Re:Eclipse Mosquitto – An open source MQTT broker
by fires10 on Sunday November 15, 2026 @03:57PM
(#50510677)
We use HiveMQ and some mosquito. Rabbitmq did not have good qos2 support. I would like to see more options in this space. Mosquito did not have good cluster support from my perspective.
Re:Eclipse Mosquitto – An open source MQTT broker
by ycombinatorx7w5 on Monday November 16, 2026 @06:31AM
(#50516403)
I fixed all this + way more: Shameless promotion for my bridge
Nats MQTTv5 with support websockets and other improvements are near first alpha release
https://github.com/nberlee/mqtt-nats-broker
Re:Eclipse Mosquitto – An open source MQTT broker
by alentred on Sunday November 15, 2026 @02:45PM
(#50510000)
Since we are into it, just sharing then: I had a lot of success with RabbitMQ + it's MQTT plugin. AFAIK, it actually has the MQTT plugin now baked in by default. Never had any issue at scale, plus you get AMQP in your stack, and you can actually use AMQP to consume the messages originally received over MQTT.
Re:Eclipse Mosquitto – An open source MQTT broker
by burcsahinoglu on Sunday November 15, 2026 @03:37PM
(#50510440)
I had a terrible time with a cluster of RabbitMQ servers, the cluster was partitioning often, impacting the application. It seemed like it was very sensitive to transient network problems.
At the end we moved from a cluster to a single instance running on a over provisioned machine, that worked pretty well.
Re:Eclipse Mosquitto – An open source MQTT broker
by jorl17 on Sunday November 15, 2026 @04:40PM
(#50511098)
At a previous job (many years ago) we used to run RabbitMQ. I hadn't configured it originally, but I was certainly left with it in pieces when it entered split-brain mode in the face of some bizarre network failure.
So we had our application talking to two nodes of a cluster, both working normally without talking to each other (nevermind the fact that the connectivity between the machines was fine). Some workers picked up jobs, others didn't. IIRC the app read requests from a queue and wrote replies to another one, so we'd have half of the jobs being picked up, and then half of the replies not being picked up (ergo, 75% of the requests failed). It was bizarre and nothing seemed to indicate there were issues with RabbitMQ itself. I don't even remember how we figured it out at the time.
It's been nearly 10 years, I'm sure that it's better, that I was inexperienced, that the original setup wasn't great. But that left me so sore on it that I have actively avoid it ever since.
Bonus points for having dealt with this while Django Celery apparently had two independent configuration mechanisms, and both were being used in this app. Fun times.
Re:Eclipse Mosquitto – An open source MQTT broker
by InsidiousWombat on Sunday November 15, 2026 @08:26PM
(#50512918)
The broker is the point.
brokerless is nice niche for when you have pretty constrained use case but just not traversing network well (zmq requires multipath for any sensible patterns) already roots many use cases out, as is the authentication
Re:Eclipse Mosquitto – An open source MQTT broker
by Kinrany on Monday November 16, 2026 @05:52AM
(#50516189)
Sure, you want a broker in most cases, but doesn't it seem wrong that the protocol has to know that? The broker shouldn't be much more than a combination of a router and a dumb pipe.
Re:Eclipse Mosquitto – An open source MQTT broker
by coderenegade on Sunday November 15, 2026 @08:30PM
(#50512947)
Depends on the task. For one-to-one comms you could use zmq, but if you need one-to-many, mqtt is a lot better. Mqtt also scales nicely after the fact, as you can hook additional services in without disrupting what's already in place.
Re:Eclipse Mosquitto – An open source MQTT broker
by stevekemp on Monday November 16, 2026 @05:09AM
(#50515935)
It depends on the use-case. I've spent the past few days setting up home automation with some cheap zigbee devices.
There are a bunch of options but the one I settled on is zigbee2mqtt, which requires a broker for message-exchange. Once it was setup it was pretty trivial to write simple clients to connect to the mosquitto instance and read/modify device state.
(e.g. I wanted something that would turn on my bedside light at 6am, and something else that would trigger some flashing lights when my laundry machine was finished and I did that via some external processes.)
Re:Eclipse Mosquitto – An open source MQTT broker
by keithnz on Sunday November 15, 2026 @04:30PM
(#50511002)
I've used this for quite a while as a gateway for sparkplugB such that things like ignition can pull our telemetry data (we do agtech monitoring, smart meters, power, water, soil moisture, temp, etc etc)
Re:Eclipse Mosquitto – An open source MQTT broker
by eska on Monday November 16, 2026 @08:15AM
(#50517292)
Curious, do you have any standards particular to agtech? In manufacturing I also just went with mqtt+sparkplug and buttblasted the entire competition struggling with opc-ua.
Re:Eclipse Mosquitto – An open source MQTT broker
by keithnz on Monday November 16, 2026 @03:16PM
(#50522564)
no, no real standards that I know of, we support a relatively flexible way on how to push tags to fit a customers standard. I know the MQTT Ignition gateway had a bunch of bugs with sparkplugb initially that got fixed, which is odd as they came up with the standard. It's not super common in agtech except for water districts which operate large pumping systems and tend to use things like Ignition. We don't have too many people who integrate using it. Not surprised you beat out the opc crowd!
Re:Eclipse Mosquitto – An open source MQTT broker
by k0morebi on Sunday November 15, 2026 @05:25PM
(#50511498)
Oh boy. You're going to hate to know what programming language is used for apache, nginx, postfix, postgres, MySQL/mariadb, redis, wireguard and the majority of network hardware.
Re:Eclipse Mosquitto – An open source MQTT broker
by jon-wood on Monday November 16, 2026 @05:35AM
(#50516091)
It depends what you mean by scaling. Mosquitto is impressively performant so you can go a long way just running a single instance on a server with a decent chunk of RAM and a reasonable CPU.
HA is a more difficult thing to solve, I believe Cedalo sell a version with HA support which may solve all this but the open source version doesn’t really have any good answers. The usual approach seems to be setting up topic replication between all your nodes and putting a load balancer in front.
Thankfully the system I’m responsible for can tolerate outages so we just work on the basis that we have regular snapshots and can stand up a new instance if the one handling traffic fails, with the fault tolerance sitting on the client side with messages being queued for transmission when the connection comes back.
Re:Eclipse Mosquitto – An open source MQTT broker
by maxpert on Sunday November 15, 2026 @07:30PM
(#50512515)
Shameless plug I've implemented https://github.com/maxpert/strangeq with AMQP and plan to integrate MQTT as supported protocol for StrangeQ. Right now I was focused on really optimizing the implementation itself (which I did), MQTT + replication/distribution is next on my list.
Re:Eclipse Mosquitto – An open source MQTT broker
by petre on Monday November 16, 2026 @04:01AM
(#50515527)
The problem we had was provisioning user accounts and topic ACLs on the broker over a HTTP API from another application. We used EMQX 5.9 and the mnesia backend to accomplish this. Mosquitto has an auth bakend but can only do this over MQTT.
I hadn't heard of it, and thought to share it. I'm not sure why people are upvoting it - but it's not impossible that others are interested too in this topic..! Cheers
[0] https://github.com/wind-c/comqtt/
[1] https://github.com/fhmq/hmq
At the end we moved from a cluster to a single instance running on a over provisioned machine, that worked pretty well.
So we had our application talking to two nodes of a cluster, both working normally without talking to each other (nevermind the fact that the connectivity between the machines was fine). Some workers picked up jobs, others didn't. IIRC the app read requests from a queue and wrote replies to another one, so we'd have half of the jobs being picked up, and then half of the replies not being picked up (ergo, 75% of the requests failed). It was bizarre and nothing seemed to indicate there were issues with RabbitMQ itself. I don't even remember how we figured it out at the time.
It's been nearly 10 years, I'm sure that it's better, that I was inexperienced, that the original setup wasn't great. But that left me so sore on it that I have actively avoid it ever since.
Bonus points for having dealt with this while Django Celery apparently had two independent configuration mechanisms, and both were being used in this app. Fun times.
brokerless is nice niche for when you have pretty constrained use case but just not traversing network well (zmq requires multipath for any sensible patterns) already roots many use cases out, as is the authentication
There are a bunch of options but the one I settled on is zigbee2mqtt, which requires a broker for message-exchange. Once it was setup it was pretty trivial to write simple clients to connect to the mosquitto instance and read/modify device state.
(e.g. I wanted something that would turn on my bedside light at 6am, and something else that would trigger some flashing lights when my laundry machine was finished and I did that via some external processes.)
I looked at MQTT options earlier last year, and the best one was Mochi ( https://github.com/mochi-mqtt/server ), written in Go.
I added TLS support with Let's Encrypt provisioning to it: https://github.com/Cyberax/lenc-mochi
For services that can't be avoided, I try to limit their exposure. I run Postgres with strictly controlled network access. Same for Redis.
What else? I'm also using Hickory for DNS. I replaced the stock OpenSSH with a version compiled using Fil-C.
i picked mosquitto but had to ditch it for AWS IoT Core and have not looked back.
HA is a more difficult thing to solve, I believe Cedalo sell a version with HA support which may solve all this but the open source version doesn’t really have any good answers. The usual approach seems to be setting up topic replication between all your nodes and putting a load balancer in front.
Thankfully the system I’m responsible for can tolerate outages so we just work on the basis that we have regular snapshots and can stand up a new instance if the one handling traffic fails, with the fault tolerance sitting on the client side with messages being queued for transmission when the connection comes back.