2 ms·

My apologies on the VerneMQ comment. I misread the sentence, not realizing it being a specific suggestion by you. Regarding the topic of MQTT in general, to me

My apologies on the VerneMQ comment. I misread the sentence, not realizing it being a specific suggestion by you. Regarding the topic of MQTT in general, to me it sounded as if you were not adding information but criticizing the choice of WebSocket instead of MQTT in this project. It was a misunderstanding. To add to the discussion, maybe you could help me a bit with an issue I'm having. I'm currently working on a service which is starting to make use of MQTT for microservices communication. Initially I was using a WebSocket server for this, then moved over to RabbitMQ a couple of years ago, and now I have added a Mosquitto server which is working, but has not yet replaced RabbitMQ. This service also has one public NodeJS websocket server for web browser clients to connect to it, this WebSocket server receives the messages via RabbitMQ and dispatches it to the clients. I also want to replace that WebSocket server by another Mosquitto instance, so that MQTT will basically become the main way for communication between servers and also with clients. I chose Mosquitto because it have been using it at home without any problems for a while now and have a custom authentication plug-in for it which I wanted to reuse. VerneMQ is a candidate, but Mosquitto is working just fine, so I haven't looked into it again. I like how lean Mosquitto is and how it's configured inside a container. Plus I can understand the source code and eventually modify it. Would you advise me against using Mosquitto in a production system? Which benefit would I have by using VerneMQ? My apologies, again.

siscia 8y ago
Don't worry! We are all busy and sometimes is normal to read too quickly a message on internet. My advice would be to have one single broker no matter what, so don't replace the websockets server with another instace of mosquitto, but just use the same old instance. Then, the ice thing of working with a protocol is that you don't care of the implementation, hence just keep using mosquitto until it support the load and the, eventually swap verneMQ if necessary. Be careful with your custom authentication logic, that if you want to migrate will require you to port it over. Verne provide plugins for Auth so it is not an huge deal but you need to think a little bit ahead. But again, if mosquitto is working fine just keep it! Cheers!

siscia 8y ago

Don't worry! We are all busy and sometimes is normal to read too quickly a message on internet. My advice would be to have one single broker no matter what, so don't replace the websockets server with another instace of mosquitto, but just use the same old instance. Then, the ice thing of working with a protocol is that you don't care of the implementation, hence just keep using mosquitto until it support the load and the, eventually swap verneMQ if necessary. Be careful with your custom authentication logic, that if you want to migrate will require you to port it over. Verne provide plugins for Auth so it is not an huge deal but you need to think a little bit ahead. But again, if mosquitto is working fine just keep it! Cheers!