MQTT has become a widely used messaging protocol for the Internet of Things (IoT). The first version of the protocol was authored by Andy Stanford-Clark of IBM and Arlen Nipper in 1999. It was originally designed with a focus on minimizing battery consumption and bandwidth usage while keeping the protocol lightweight.
MQTT uses a publish/subscribe messaging model and runs on top of TCP/IP. Unlike traditional message-queue-based systems, publishers and subscribers communicate through a broker, which manages message delivery between them. Today, MQTT is widely used by embedded systems and IoT devices for communication.
I’ve been working with MQTT for the past three months, and I recently decided to run my own MQTT broker on a Raspberry Pi.
What is Broker?
Basically brokers carry out messages using publish/subscribe model. The main tasks of broker is responsible for receiving all messages, filtering and accessing control that decide who can let in or not. Also it holds some clients sessions persisted in-memory or optionally in databases (SQLite, MySQL, etc). These are some popular brokers.
- http://mosquitto.org (used by Amazon IoT)
- http://www.hivemq.com
- http://www.rabbitmq.com
- https://developer.ibm.com/messaging/messagesight/
My choice is Mosca to try. Normally I use Mosquitto broker but I’m really curious to use Javascript based broker. I’m not sure how fast as Mosquitto. I’ll let it try on my Raspberry Pi.
Here is link: http://mosca.azmicirit.com