Need advice about which tool to choose?Ask the StackShare community!
Pulsar vs Pusher: What are the differences?
What is Pulsar? Distributed solution providing messaging and queuing for streaming data. Apache Pulsar is a distributed messaging solution developed and released to open source at Yahoo. Pulsar supports both pub-sub messaging and queuing in a platform designed for performance, scalability, and ease of development and operation.
What is 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.
Pulsar and Pusher belong to "Realtime Backend / API" category of the tech stack.
Some of the features offered by Pulsar are:
- Unified model supporting pub-sub messaging and queuing
- Easy scalability to millions of topics
- Native multi-datacenter replication
On the other hand, Pusher provides the following key features:
- Easily build scalable in-app notifications, chat, realtime graphs, geotracking and more in your web & mobile apps with our hosted pub/sub messaging API.
- Send programmable push notifications to iOS and Android devices with delivery and open rate tracking built in.
- Easily add 1-1 and group Chat to your web & mobile apps. Presence, message storage, rich media, notifications, typing indicators and more.
Pulsar is an open source tool with 3.77K GitHub stars and 862 GitHub forks. Here's a link to Pulsar's open source repository on GitHub.
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 Apache Pulsar
- Simple7
- Scalable4
- High-throughput3
- Geo-replication2
- Multi-tenancy2
- Pulsar Functions1
- Secure1
- Stream SQL1
- Horizontally scaleable1
- Easy to deploy1
- Fast1
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 Apache Pulsar
- Very few commercial vendors for support1
- LImited Language support(6)1
- No one and only one delivery1
- No guaranteed dliefvery1
- Not jms compliant1
- Only Supports Topics1
Cons of Pusher
- Costly11