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

MQTT

357
387
+ 1
4
SignalR

406
987
+ 1
108
Add tool

MQTT vs SignalR: What are the differences?

MQTT: 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; SignalR: A new library for ASP.NET developers that makes developing real-time web functionality easy. SignalR allows bi-directional communication between server and client. Servers can now push content to connected clients instantly as it becomes available. SignalR supports Web Sockets, and falls back to other compatible techniques for older browsers. SignalR includes APIs for connection management (for instance, connect and disconnect events), grouping connections, and authorization.

MQTT belongs to "Message Queue" category of the tech stack, while SignalR can be primarily classified under "Realtime Backend / API".

SignalR is an open source tool with 7.75K GitHub stars and 2.19K GitHub forks. Here's a link to SignalR's open source repository on GitHub.

simplement-e, Jet.com, and NRGSoft are some of the popular companies that use SignalR, whereas MQTT is used by Pubu, Jaumo, and Danale Inc. SignalR has a broader approval, being mentioned in 22 company stacks & 18 developers stacks; compared to MQTT, which is listed in 12 company stacks and 6 developer stacks.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of MQTT
Pros of SignalR
  • 2
    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
  • 25
    Supports .NET server
  • 17
    Real-time
  • 13
    Free
  • 13
    Fallback to SSE, forever frame, long polling
  • 12
    WebSockets
  • 7
    Simple
  • 7
    JSON
  • 6
    Open source
  • 4
    Ease of use
  • 4
    Cool

Sign up to add or upvote prosMake informed product decisions

Cons of MQTT
Cons of SignalR
  • 1
    Easy to configure in an unsecure manner
  • 2
    Requires jQuery
  • 2
    Expertise hard to get
  • 1
    Weak iOS and Android support
  • 1
    Big differences between ASP.NET and Core versions

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

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 SignalR?

SignalR allows bi-directional communication between server and client. Servers can now push content to connected clients instantly as it becomes available. SignalR supports Web Sockets, and falls back to other compatible techniques for older browsers. SignalR includes APIs for connection management (for instance, connect and disconnect events), grouping connections, and authorization.

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

What companies use MQTT?
What companies use SignalR?
See which teams inside your own company are using MQTT or SignalR.
Sign up for Private StackShareLearn More

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

What tools integrate with MQTT?
What tools integrate with SignalR?

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

What are some alternatives to MQTT and SignalR?
RabbitMQ
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
REST
An architectural style for developing web services. A distributed system framework that uses Web protocols and technologies.
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.
See all alternatives