What is MQTT?
It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium.
MQTT is a tool in the Message Queue category of a tech stack.
Who uses MQTT?
9 companies use MQTT in their tech stacks, including Pubu, Jaumo, and Danale Inc.
Why developers like MQTT?
Here’s a list of reasons why companies and developers use MQTT
Be the first to leave a pro
MQTT Alternatives & Comparisons
What are some alternatives to MQTT?
See all alternatives
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
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 is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.
Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.
No related comparisons found
- No public GitHub repository available -