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

NATS

Stacks85

Followers86

+ 1

Votes35

Pusher

Stacks323

Followers238

+ 1

Votes200

Add tool

NATS vs Pusher: What are the differences?

NATS: 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; Pusher: Hosted APIs to build realtime apps with less code. Pusher is the category leader in delightful APIs for app developers building communication and collaboration features.

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

"Fastest pub-sub system out there" is the top reason why over 13 developers like NATS, while over 44 developers mention "An easy way to give customers realtime features" as the leading cause for choosing Pusher.

Product Hunt, Groupon, and Buffer are some of the popular companies that use Pusher, whereas NATS is used by Apcera, Workiva, and Bridgevine. Pusher has a broader approval, being mentioned in 125 company stacks & 42 developers stacks; compared to NATS, which is listed in 26 company stacks and 12 developer stacks.

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

Pusher is the category leader in delightful APIs for app developers building communication and collaboration features.

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

Why do developers choose NATS?

Why do developers choose Pusher?

15
Fastest pub-sub system out there
12
Rock solid
8
Easy to grasp
0
Easy, Fast, Secure

Add a pro

45
An easy way to give customers realtime features
36
Websockets
34
Simple
25
Easy to get started with
21
Free plan
10
Heroku Add-on
9
Easy and fast to configure and to understand

Add a pro

Sign up to add, upvote and see more prosMake informed product decisions

What are the cons of using NATS?

What are the cons of using Pusher?

Be the first to leave a con

Add a con

Be the first to leave a con

Add a con

What companies use NATS?

What companies use Pusher?

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

What tools integrate with NATS?

What tools integrate with Pusher?

No integrations found

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

What are some alternatives to NATS and Pusher?

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

Firebase

Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds.

Socket.IO

It enables real-time bidirectional event-based communication. It works on every platform, browser or device, focusing equally on reliability and speed.

Google Cloud Pub/Sub

Cloud Pub/Sub is a fully-managed real-time messaging service that allows you to send and receive messages between independent applications. You can leverage Cloud Pub/Sub’s flexibility to decouple systems and components hosted on Google Cloud Platform or elsewhere on the Internet.

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.

See all alternatives

Decisions about NATS and Pusher

No stack decisions found

Related Comparisons

Interest over time

Reviews of NATS and Pusher

No reviews found

How developers use NATS and Pusher

Nathan Heffley uses

Pusher

In the original prototype all the communication was handled by a backend server. Each client connected directly to the server using the socket.io library. This quickly proved to be messy and unreliable, especially on the cheap server being used to host it.

Websockets proved to be a little more reliable, but still just as messy and not all browsers support them. That's when the project was switched over to use Pusher. Using Pusher has allowed all but the initial connection code to be off-loaded onto the client. Now instead of communicating through a self-hosted server, clients can communicate pretty much peer-to-peer over Pusher.