Pusher vs Pushpin: What are the differences?
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; Pushpin: Reverse proxy for realtime web services. Pushpin is a reverse proxy server that makes it easy to build realtime web services. The project is unique among realtime push solutions in that it is designed to address the needs of API creators.
Pusher and Pushpin belong to "Realtime Backend / API" category of the tech stack.
Some of the features offered by Pusher are:
- 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.
On the other hand, Pushpin provides the following key features:
- Supports HTTP streaming, HTTP long-polling, and WebSockets.
- Clients communicate using your API contract. Pushpin is a server-side implementation detail.
- Since Pushpin is a proxy server, the backend can be written in any language.
Pushpin is an open source tool with 2.53K GitHub stars and 96 GitHub forks. Here's a link to Pushpin's open source repository on GitHub.
What is Pusher?
What is Pushpin?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Pusher?
What are the cons of using Pushpin?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Pushpin?
Sign up to get full access to all the tool integrationsMake informed product decisions
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.
Pusher is used to send update notification whenever Lapzbot joins a server.