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

NATS

237
363
+ 1
51
SignalR

412
992
+ 1
108
Add tool

NATS vs SignalR: What are the differences?

Developers describe NATS as "Lightweight publish-subscribe & distributed queueing messaging system". Unlike traditional enterprise messaging systems, NATS has an always-on dial tone that does whatever it takes to remain available. This forms a great base for building modern, reliable, and scalable cloud and distributed systems. On the other hand, SignalR is detailed as "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.

NATS and SignalR can be primarily classified as "Realtime Backend / API" tools.

"Fastest pub-sub system out there" is the primary reason why developers consider NATS over the competitors, whereas "Supports .NET server" was stated as the key factor in picking SignalR.

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

According to the StackShare community, NATS has a broader approval, being mentioned in 27 company stacks & 11 developers stacks; compared to SignalR, which is listed in 20 company stacks and 16 developer stacks.

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of NATS
Pros of SignalR
  • 20
    Fastest pub-sub system out there
  • 14
    Rock solid
  • 10
    Easy to grasp
  • 3
    Light-weight
  • 3
    Easy, Fast, Secure
  • 1
    Robust Security Model
  • 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 NATS
Cons of SignalR
  • 1
    No Order
  • 1
    Persistence with Jetstream supported
  • 1
    No Persistence
  • 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 NATS?

Unlike traditional enterprise messaging systems, NATS has an always-on dial tone that does whatever it takes to remain available. This forms a great base for building modern, reliable, and scalable cloud and distributed systems.

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 NATS?
What companies use SignalR?
See which teams inside your own company are using NATS 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 NATS?
What tools integrate with SignalR?
What are some alternatives to NATS and SignalR?
Kafka
Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.
gRPC
gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking...
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.
NSQ
NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.
RabbitMQ
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
See all alternatives