Need advice about which tool to choose?Ask the StackShare community!

MQTT

416
477
+ 1
5
REST

20
176
+ 1
0
Add tool

MQTT vs REST: What are the differences?

Developers describe MQTT as "A machine-to-machine Internet of Things connectivity protocol". 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. On the other hand, REST is detailed as "A software architectural style". An architectural style for developing web services. A distributed system framework that uses Web protocols and technologies.

MQTT and REST are primarily classified as "Message Queue" and "Remote Procedure Call (RPC)" tools respectively.

Pubu, Jaumo, and Danale Inc are some of the popular companies that use MQTT, whereas REST is used by Zalando, ScoreBeyond, and Mercedes-Benz.io GmbH. MQTT has a broader approval, being mentioned in 12 company stacks & 6 developers stacks; compared to REST, which is listed in 9 company stacks and 5 developer stacks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of MQTT
Pros of REST
  • 3
    Varying levels of Quality of Service to fit a range of
  • 1
    Very easy to configure and use with open source tools
  • 1
    Lightweight with a relatively small data footprint
  • 3
    Popularity

Sign up to add or upvote prosMake informed product decisions

Cons of MQTT
Cons of REST
  • 1
    Easy to configure in an unsecure manner
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    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.

    What is REST?

    An architectural style for developing web services. A distributed system framework that uses Web protocols and technologies.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use MQTT?
    What companies use REST?
    See which teams inside your own company are using MQTT or REST.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with MQTT?
    What tools integrate with REST?
      No integrations found

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to MQTT and REST?
      RabbitMQ
      RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
      XMPP
      It is a set of open technologies for instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.
      Google Cloud Messaging
      Google Cloud Messaging (GCM) is a free service that enables developers to send messages between servers and client apps. This includes downstream messages from servers to client apps, and upstream messages from client apps to servers.
      Kafka
      Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
      ZeroMQ
      The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.
      See all alternatives