MQTT Broker Comparison – MQTTRoute vs Mosquitto Ranjith Kumar DSM April 24, 2019 MQTT is one of the most widely adopted protocols today in the IoT Arena. There are a lot of MQTT Brokers available for your solution implementation. Choosing the MQTT Broker that fits your criteria makes your project more than 50% complete. In an article earlier this year, we wrote about How to choose a perfect MQTT broker for your implementation. Bevywise MQTTRoute is a commercial MQTT Broker built using C and python. Similarly, Mosquitto is one of the fastest open source broker built on C. This article gives a high level overview of the MQTT Broker comparison between MQTTRoute and Mosquitto. MQTT Compliance Both Mosquitto and Bevywise are built as per MQTT protocol specification like publish message format, command messages, QoS(Quality of Service), retain, Wild card topics and error handling etc. MQTT Data Persistence IOT / IIoT is not about communication. It is about storing data for future analysis and decision-making. Mosquitto by default process all the message communication in memory. There is an option to store data of subscription into a file (mosquitto.db). But this file cannot be used outside the application. However, MQTTRoute comes with a default option to store data into MySQL, SQLite & PostgreSQL. We recommend MySQL for deployments and the application you are building can also query the database in parallel. In addition MQTTRoute allows you to write data into ElasticSearch, MongoDB or any other storage using the plugin system built into the MQTT Broker. MQTT Dashboard One of the critical issue in the MQTT Implementation today is that the manager applications are built over data received by an MQTT client that subscribe to #. But, this is not the right as the meta information of the data is lost. So this mandates the need for the MQTT Broker to be integral part of the application. Keeping this in mind, we have built the UI into the MQTT Broker. We have built a comprehensive MQTT Dashboard as part of the MQTTRoute as well as the Platform. However, Mosquitto does not have any User interface as the data persistence itself is not available. There are some third party User interfaces which are built as a client. Customization Above all, The default web interface of the MQTTRoute can be customized as needed. The Product can be white labelled. Mosquitto as a open source MQTT broker can be customized to a larger extent. But the customization is more on the C layer for the Mosquitto and all the building blocks over it need to be recreated. Bevywise MQTTRoute on the other hand allows customization at the appliation layer. Some of the customization includes changing the User interface, advanced visualization transforming data before storage, Integration Data Hooks and REST API are the two major integration end points of the Bevywise MQTT broker. MQTTRoute makes a huge leap ahead when you want to build an application over the Mosquitto. Other than REST API’s, Bevywise MQTT broker can be customizable to integrate with other MQTT based tools like Google pub/sub, Redis, tableau, modbus and more. Besides that, the cost and the effort spent on customization will be very minimal when compared to Mosquitto. MQTT Broker Performance Comparison Mosquitto is built on C and Bevywise MQTTRoute is built on a combination of C & Python for easy extendability and performance. Mosquitto is the fastest MQTT Broker available today when run as just a message broker. Bevywise MQTTRoute has a throughput at par with the Mosquitto. Support & Consulting MQTTRoute comes with a FREE Support where in we do consluting for your implementation while you will not be getting these supports on the Open Source Brokers. MQTT Broker comparison Table Features MQTTRoute Mosquitto Protocol MQTT, Web socket MQTT, WebSocket Visualize of Data In built Dashboard with details of Devices level. Manage devices with send command, create Rules via UI. Customizable. thrid party plugin Security TLS/SSL, device level Authentication TLS / SSL , device level authentication Inbuilt Storage Options MySQL / SQLite / PostgreSQL Allows Third-party application to read. Store data in-memory & File Only for Internal purpose Extendable data Storage Extension based Storage using Cusotm_storage option. Prebuilt connectors available in Github. third party plugins for Storage OS Windows, Windows server, Linux, Mac and Raspberry Pi Linux, Mac, Windows and BSD Rule Engine YES. Custom Rules can be added from the User Interface. No Error Log YES. Time Out errors , Authentication, Packet errors are deducted and shown on the UI. Yes, Enabled at the conf file and show in the Terminal Localization Yes. Option to customize to any language No Clustering Yes. No. One used as a single cluster SaaS based Yes. IoT Platform supports SaaS based Scalable architecture No. Throttling Developed and will be available in Q3, 2019. Yes Complete MQTT Standard Support Yes Yes Integration REST API , Data Plugins Only DATA Plugins Docker Support Yes Yes Whitelabel Yes Yes Open source No Yes Built on C / Python language C language MQTT version Current support MQTT 3.1.1 and MQTT 5 coming soon Current support MQTT 3.1.1 and MQTT 5 coming soon Support 24×7 live support via Telephone, Whattsapp, Email. Forum support The overall MQTT Broker comparison between MQTTRoute & Mosquitto will help you choose the best one for your IoT implementation. You can try the Bevywise MQTTRoute by downloading it FREE now Must Read Other Related Post Docker MQTT Broker for easy service manageability Choosing Best MQTT Broker for your IoT Implementation Lower Power consumption MQTT vs REST from IoT Implementation perspective Creating SSL Certificates for Secure MQTT communication MQTT Broker integration using REST API Feel free to write to support for any questions / suggestions. Leave a Reply Cancel replyYour email address will not be published. Required fields are marked *Comment Name * Email * Website Save my name, email, and website in this browser for the next time I comment.