3 ms·
I wrote a very simple queue for embedded devices to talk to (in Go, so you just copy the single binary), which is similar to VerneMQ (I guess) but way less comp
by StavrosK 11y ago
I wrote a very simple queue for embedded devices to talk to (in Go, so you just copy the single binary), which is similar to VerneMQ (I guess) but way less complex:
http://www.stavros.io/posts/messaging-for-your-things/ http://www.stavros.io/posts/messaging-for-your-things/
It's basically an HTTP API for polling pub/sub, along with a streaming endpoint for push.
- fasteo 11y ago>>> which is similar to VerneMQ (I guess) but way less complex I quick read of both VerneMQ and your queue service indicates that your guess is wrong: - The whole MQTT spec (compact on-the-air messages, hierarchical topics, wildcard subscriptions, QoS level, message persistence) - Service level agreement - Live code upgrade - Monitoring and tracing built-in - Extensible with plug-ins - Fault tolerance