What is Pusher and what are its top alternatives?
Top Alternatives to Pusher
- PubNub
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
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
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
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. ...
- 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. ...
- ws
It is a simple to use, blazing fast, and thoroughly tested WebSocket client and server implementation. ...
Pusher alternatives & related posts
- Massively scalable & easy to use36
- Easy setup25
- Reliable20
- Great support19
- Flexible to integrate to custom applications14
- High-Performance13
- Sockets at Scale13
- 99.999% availability guarantees13
- High-Reliability12
- Multiplexing12
- Scalability7
- 70+ SDKs5
- High-Availability5
- Azure Add-on4
- Security4
- Heroku Add-on3
- Easy to setup3
- Flexible3
- Presence3
- Data Streams2
- Free Plan2
- Server-Side Cache2
- PhoneGap Plugin2
- AngularJS Adapter2
- Data Sync2
- Analytics2
- Support2
- Easy integration with iOS apps1
- Easy setup and very reliable1
- High cost, going up more in Summer '151
- Cool1
- Angular 2+ integration1
- Documentation, easy to use, great people/service1
- CTO stephen also is A++++++1
- Real time and easy to use.1
- Cdsd1
- Costly1
SignalR
- Supports .NET server29
- Real-time22
- Free16
- Fallback to SSE, forever frame, long polling15
- WebSockets14
- Simple10
- Open source8
- JSON8
- Ease of use7
- Cool5
- Azure0
- Expertise hard to get2
- Requires jQuery2
- Weak iOS and Android support1
- Big differences between ASP.NET and Core versions1
related SignalR posts
We need to interact from several different Web applications (remote) to a client-side application (.exe in .NET Framework, Windows.Console under our controlled environment). From the web applications, we need to send and receive data and invoke methods to client-side .exe on javascript events like users onclick. SignalR is one of the .Net alternatives to do that, but it adds overhead for what we need. Is it better to add SignalR at both client-side application and remote web application, or use gRPC as it sounds lightest and is multilingual?
SignalR or gRPC are always sending and receiving data on the client-side (from browser to .exe and back to browser). And web application is used for graphical visualization of data to the user. There is no need for local .exe to send or interact with remote web API. Which architecture or framework do you suggest to use in this case?
- Realtime backend made easy369
- Fast and responsive268
- Easy setup240
- Real-time213
- JSON188
- Free133
- Backed by google126
- Angular adaptor82
- Reliable67
- Great customer support35
- Great documentation31
- Real-time synchronization25
- Mobile friendly21
- Rapid prototyping18
- Great security14
- Automatic scaling12
- Freakingly awesome11
- Angularfire is an amazing addition!8
- Super fast development8
- Chat8
- Firebase hosting6
- Built in user auth/oauth6
- Awesome next-gen backend6
- Ios adaptor6
- Very easy to use4
- Speed of light4
- Great3
- It's made development super fast3
- Brilliant for startups3
- .net2
- JS Offline and Sync suport2
- Low battery consumption2
- Push notification2
- Free hosting2
- Cloud functions2
- The concurrent updates create a great experience2
- I can quickly create static web apps with no backend2
- Great all-round functionality2
- Free authentication solution2
- CDN & cache out of the box1
- Google's support1
- Simple and easy1
- Faster workflow1
- Free SSL1
- Easy Reactjs integration1
- Easy to use1
- Large1
- Serverless1
- Good Free Limits1
- Can become expensive31
- No open source, you depend on external company16
- Scalability is not infinite15
- Not Flexible Enough9
- Cant filter queries7
- Very unstable server3
- No Relational Data3
- Too many errors2
- No offline sync2
related Firebase posts
Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.
My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.
This is my stack in Application & Data
JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB
My Utilities Tools
Google Analytics Postman Elasticsearch
My Devops Tools
Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack
My Business Tools
Slack
- Reasonable Pricing15
- Threads14
- Very fast and scalable13
- SDKs for React, RN, Android and iOS are better13
- Reactions13
- Front-End Components10
- Great support9
- Stability4
- Performance4
related Chat by Stream posts
- Powerful, simple, and well documented api147
- RESTful API88
- Clear pricing66
- Great sms services61
- Low cost of entry58
- Global SMS Gateway29
- Good value14
- Cloud IVR12
- Simple11
- Extremely simple to integrate with rails11
- Great for startups6
- SMS5
- Great developer program3
- Hassle free3
- Text me the app pages2
- New Features constantly rolling out1
- Many deployment options, from build from scratch to buy1
- Easy integration1
- Two factor authentication1
- Predictable pricing4
- Expensive2
related Twilio posts
Hi, We are looking to implement 2FA - so that users would be sent a Verification code over their Email and SMS to their phone.
We faced some limitations with Amazon SNS where we could either send the verification code to email OR to the phone number, while we want to send it to both.
We also are looking to make the 2FA more flexible by adding any other options later on.
What are the best alternatives to SNS for this use case and purpose? Looked at Twilio but want to explore other options before making a decision.
Would be great to know what the experience with Twilio has been, especially the limitations/issues with Twilio...
Appreciate any input from users of Twilio and others who have had similar use cases.
Hi, Stackshare community, I plan to build an app where people can go live, and users can watch him, 1 to many, follow each other, and text.
I am expecting a huge number of users to use the app in the first month (100k+)
I made the UX/UI design, and my designer asked me to find a developer.
I want your advice. What server is the best for video quality and fast text messages (like uplive, bigo)?
Ex. Agora, Twilio, Amazon Chime, Aws, or fiberbass
I need for both operating systems, (ios, android). Do you recommend Flutter?
- I have AWS server in my country (Bahrain), and 80% of the audience are from the same area. Does it help in the video quality between the audience?
Thank you for this helpful website.
- Real-time217
- Event-based communication141
- Node.js141
- WebSockets102
- Open source101
- Binary streaming26
- No internet dependency21
- Large community10
- Fallback to polling if WebSockets not supported9
- Push notification6
- Ease of access and setup5
- Bad documentation11
- Githubs that complement it are mostly deprecated4
- Doesn't work on React Native3
- Small community2
- Websocket Errors2
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.
Google Cloud Pub/Sub
- Easy to set-up and start with9
- A great choice for microservice architecture2
- Efficient and practical for complex systems2
- Need integration with stackdriver for monitoring2
related Google Cloud Pub/Sub posts
Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?