What is VerneMQ?
VerneMQ is a distributed MQTT message broker, implemented in Erlang/OTP. It's open source, and Apache 2 licensed. VerneMQ implements the MQTT 3.1, 3.1.1 and 5.0 specifications.
VerneMQ is a tool in the Message Queue category of a tech stack.
VerneMQ is an open source tool with 2K GitHub stars and 219 GitHub forks. Here’s a link to VerneMQ's open source repository on GitHub
Who uses VerneMQ?
6 companies reportedly use VerneMQ in their tech stacks, including Haptik, Cantiz IoT Platform, and Teleolabs.
8 developers on StackShare have stated that they use VerneMQ.
Why developers like VerneMQ?
Here’s a list of reasons why companies and developers use VerneMQ
- Open Source, Apache 2 licensed
- QoS 0, QoS 1, QoS 2
- MQTT v5.0 fully implemented
- Basic Authentication and Authorization
- Bridge Support
- $SYS Tree for monitoring and reporting
- TLS (SSL) Encryption
- Websockets Support
- Cluster Support with sophisticated self-healing mechanisms
- Queue Migration
- Prometheus Monitoring
- Logging (Console, Files, Syslog)
- Reporting to Graphite
- Extensible Plugin architecture (Erlang, Elixir, Lua)
- WebHooks Plugins
- Multiple Sessions per ClientId
- Shared Subscriptions
- Proxy Protocol v1, v2
VerneMQ Alternatives & Comparisons
What are some alternatives to VerneMQ?
See all alternatives
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
It is lightweight and is suitable for use on all devices from low power single board computers to full servers.. The MQTT protocol provides a lightweight method of carrying out messaging using a publish/subscribe model. This makes it suitable for Internet of Things messaging such as with low power sensors or mobile devices such as phones, embedded computers or microcontrollers.
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
It is fully open source and licensed under the Apache Version 2.0. It implements both MQTT V3.1 and V3.1.1 protocol specifications, and supports MQTT-SN, CoAP, WebSocket, STOMP and SockJS at the same time.
Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.