VerneMQWhat 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 Background Jobs category of a tech stack.
Key Features
Open Source, Apache 2 licensedQoS 0, QoS 1, QoS 2MQTT v5.0 fully implementedBasic Authentication and AuthorizationBridge Support$SYS Tree for monitoring and reportingTLS (SSL) EncryptionWebsockets SupportCluster Support with sophisticated self-healing mechanismsQueue MigrationPrometheus MonitoringLogging (Console, Files, Syslog)Reporting to GraphiteExtensible Plugin architecture (Erlang, Elixir, Lua)WebHooks PluginsMultiple Sessions per ClientIdShared SubscriptionsProxy Protocol v1, v2
VerneMQ Pros & Cons
Pros of VerneMQ
- ✓Fully open source clustering
- ✓MQTT v5 implementation
- ✓Open Source Message and Metadata Persistence
- ✓Open Source Plugin System
- ✓Open source shared subscriptions
- ✓Proxy Protocol support
Cons of VerneMQ
No cons listed yet.
VerneMQ Alternatives & Comparisons
What are some alternatives to VerneMQ?
Kafka
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
RabbitMQ
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
Amazon SQS
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.
Celery
Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.
