Need advice about which tool to choose?Ask the StackShare community!
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.
I am building an IoT application that will utilize connected air quality sensors to provide real-time indoor air quality in offices. I want to be able to share this data with a few different databases, etc.
Wondering if anyone has any advice on which real-time streaming API would be best for this sort of application, or even how I should think about it?
For IoT, we support MQTT along with websockets and SSE. The pattern you're suggesting that involves harvesting data from devices and soaking into a database is easy to achieve with one of the Ably integrations (Serverless functions/webhook) . Here are some tutorials to do things like this: https://ably.com/tutorials/reactor-event-zapier#step2-mqtt-ably
We use Pusher at www.justlearn.com. It works fine. When you reach more users, Pusher gets expensive. We use Pusher for live chat between users. Their software is easy to use. We have had issues with auth on Pusher.
Pros of NATS
- Fastest pub-sub system out there22
- Rock solid16
- Easy to grasp12
- Light-weight4
- Easy, Fast, Secure4
- Robust Security Model2
Pros of Pusher
- An easy way to give customers realtime features55
- Websockets40
- Simple34
- Easy to get started with27
- Free plan25
- Heroku Add-on12
- Easy and fast to configure and to understand11
- JSON9
- Happy6
- Azure Add-on6
- Support5
- Push notification4
Sign up to add or upvote prosMake informed product decisions
Cons of NATS
- Persistence with Jetstream supported2
- No Order1
- No Persistence1
Cons of Pusher
- Costly10
Sign up to add or upvote consMake informed product decisions
What is NATS?
What is Pusher?
Need advice about which tool to choose?Ask the StackShare community!
What companies use NATS?
What companies use Pusher?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+34
+26