What is Pusher and what are its top alternatives?
Top Alternatives to Pusher
PubNub makes it easy for you to add real-time capabilities to your apps, without worrying about the infrastructure. Build apps that allow your users to engage in real-time across mobile, browser, desktop and server. ...
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. ...
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. ...
Chat by Stream
Chat API and SDK. With a beautiful UI Kit, easy to use React Components and powerful API. Add Chat to any application in a matter of hours. The tech uses Go, RocksDB and Raft. By the creators of Stream, the API that powers activity feeds for more than 300 million users. ...
Twilio offers developers a powerful API for phone services to make and receive phone calls, and send and receive text messages. Their product allows programmers to more easily integrate various communication methods into their software and programs. ...
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. ...
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 alternatives & related posts
- Massively scalable & easy to use33
- Easy setup24
- Great support18
- Flexible to integrate to custom applications14
- 99.999% availability guarantees12
- Sockets at Scale12
- 70+ SDKs5
- Azure Add-on4
- Heroku Add-on3
- Easy to setup3
- Data Sync2
- AngularJS Adapter2
- PhoneGap Plugin2
- Server-Side Cache2
- Free Plan2
- Data Streams2
- Easy setup and very reliable1
- Real time and easy to use.1
- High cost, going up more in Summer '151
- CTO stephen also is A++++++1
- Angular 2+ integration1
- Documentation, easy to use, great people/service1
- Easy integration with iOS apps1
related PubNub posts
Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?
I am trying to replace Socket.IO with PubNub. Provide the way to do it.
- Supports .NET server20
- Fallback to SSE, forever frame, long polling11
- Open source5
- Ease of use3
- Requires jQuery1
- Expertise hard to get1
- Weak iOS and Android support1
related SignalR posts
- Realtime backend made easy361
- Fast and responsive263
- Easy setup234
- Backed by google121
- Angular adaptor81
- Great customer support36
- Great documentation26
- Real-time synchronization23
- Mobile friendly20
- Rapid prototyping17
- Great security12
- Automatic scaling11
- Freakingly awesome10
- Angularfire is an amazing addition!8
- Super fast development8
- Awesome next-gen backend6
- Ios adaptor6
- Built in user auth/oauth5
- Firebase hosting5
- Speed of light4
- Very easy to use4
- It's made development super fast3
- Brilliant for startups3
- Great all-round functionality2
- Low battery consumption2
- I can quickly create static web apps with no backend2
- The concurrent updates create a great experience2
- JS Offline and Sync suport2
- Faster workflow1
- Free SSL1
- Good Free Limits1
- Push notification1
- Easy to use1
- Easy Reactjs integration1
- Can become expensive28
- Scalability is not infinite15
- No open source, you depend on external company14
- Not Flexible Enough9
- Cant filter queries5
- Very unstable server3
- Too many errors2
- No Relational Data2
related Firebase posts
This is my stack in Application & Data
My Utilities Tools
Google Analytics Postman Elasticsearch
My Devops Tools
Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack
My Business Tools
- Reasonable Pricing15
- Very fast and scalable13
- SDKs for React, RN, Android and iOS are better13
- Front-End Components10
- Great support9
related Chat by Stream posts
- Powerful, simple, and well documented api144
- RESTful API87
- Clear pricing66
- Great sms services61
- Low cost of entry58
- Global SMS Gateway28
- Good value14
- Cloud IVR12
- Extremely simple to integrate with rails11
- Great for startups5
- Great developer program3
- Hassle free3
- New Features constantly rolling out1
- Many deployment options, from build from scratch to buy1
- Text me the app pages1
- Easy integration1
- Two factor authentication1
- Predictable pricing1
related Twilio posts
Nexmo vs Twilio ?
Back in the early days at SmartZip Analytics, that evaluation had - for whatever reason - been made by Product Management. Some developers might have been consulted, but we hadn't made the final call and some key engineering aspects of it were omitted.
When revamping the platform, I made sure to flip the decision process how it should be. Business provided an input but Engineering lead the way and has the final say on all implementation matters. My engineers and I decided on re-evaluating the criteria and vendor selection. Not only did we need SMS support, but were we not thinking about #VoiceAndSms support as the use cases evolved.
Also, on an engineering standpoint, SDK mattered. Nexmo didn't have any. Twilio did. No-one would ever want to re-build from scratch integration layers vendors should naturally come up with and provide their customers with.
Twilio won on all fronts. Including costs and implementation timelines. No-one even noticed the vendor switch.
Many years later, Twilio demonstrated its position as a leader by holding conferences in the Bay Area, announcing features like Twilio Functions. Even acquired Authy which we also used for 2FA. Twilio's growth has been amazing. Its recent acquisition of SendGrid continues to show it.
- Event-based communication141
- Open source102
- Binary streaming26
- No internet dependency22
- Fallback to polling if WebSockets not supported9
- Large community7
- Ease of access and setup5
- Push notification4
- Bad documentation9
- Githubs that complement it are mostly deprecated4
- Doesn't work on React Native2
- Small community2
related Socket.IO posts
I use Socket.IO because the application has 2 frontend clients, which need to communicate in real-time. The backend-server handles the communication between these two clients via websockets. Socket.io is very easy to set up in Node.js and ExpressJS.
In the research project, the 1st client shows panoramic videos in a so called cave system (it is the VR setup of our research lab, which consists of three big screens, which are specially arranged, so the user experience the videos more immersive), the 2nd client controls the videos/locations of the 1st client.
We are starting to work on a web-based platform aiming to connect artists (clients) and professional freelancers (service providers). In-app, timeline-based, real-time communication between users (& storing it), file transfers, and push notifications are essential core features. We are considering using Node.js, ExpressJS, React, MongoDB stack with Socket.IO & Apollo, or maybe using Real-Time Database and functionalities of Firebase.
- Easy to set-up and start with4
- Need integration with stackdriver for monitoring2
- Fastest pub-sub system out there20
- Rock solid14
- Easy to grasp10
- Easy, Fast, Secure3
- Robust Security Model1
- Persistence with Jetstream supported1
- No Order1
- No Persistence1