What is Faye and what are its top alternatives?
Top Alternatives to Faye
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. ...
Socket.IO
It enables real-time bidirectional event-based communication. It works on every platform, browser or device, focusing equally on reliability and speed. ...
Pusher
Pusher is the category leader in delightful APIs for app developers building communication and collaboration features. ...
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. ...
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. ...
NATS
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. ...
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. ...
WCF
It is a framework for building service-oriented applications. Using this, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application. ...
Faye alternatives & related posts
- Realtime backend made easy357
- Fast and responsive261
- Easy setup233
- Real-time206
- JSON184
- Free126
- Backed by google120
- Angular adaptor80
- Reliable62
- Great customer support36
- Great documentation25
- Real-time synchronization22
- Mobile friendly19
- Rapid prototyping17
- Great security12
- Automatic scaling10
- Freakingly awesome9
- Super fast development8
- Chat8
- Angularfire is an amazing addition!8
- Awesome next-gen backend6
- Ios adaptor6
- Firebase hosting5
- Built in user auth/oauth5
- Very easy to use4
- Great3
- Speed of light3
- Brilliant for startups3
- It's made development super fast3
- Low battery consumption2
- The concurrent updates create a great experience2
- I can quickly create static web apps with no backend2
- Great all-round functionality2
- Easy Reactjs integration1
- Good Free Limits1
- .net1
- Faster workflow1
- Serverless1
- JS Offline and Sync suport1
- Easy to use1
- Large1
- Push notification1
- Can become expensive26
- No open source, you depend on external company14
- Scalability is not infinite14
- 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
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
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.
- Real-time209
- Event-based communication140
- Node.js139
- Open source101
- WebSockets99
- 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.
- An easy way to give customers realtime features50
- Websockets39
- Simple35
- Easy to get started with27
- Free plan24
- Heroku Add-on12
- Easy and fast to configure and to understand11
- JSON9
- Azure Add-on6
- Support5
- Happy5
- Push notification4
- Costly9
- Aa0
related Pusher posts
Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?
Recently we finished long research on chat tool for our students and mentors. In the end we picked Mattermost Team Edition as the cheapest and most feature complete option. We did consider building everything from scratch and use something like Pusher or Twilio on a backend, but then we would have to implement all the desktop and mobile clients and all the features oursevles. Mattermost gave us flexible API, lots of built in or easy to install integrations and future-proof feature set. We are still integrating it with our main platform but so far the team, existing mentors and students are very happy.
Google Cloud Pub/Sub
- Easy to set-up and start with4
- 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?
SignalR
- Supports .NET server16
- Real-time13
- Free11
- Fallback to SSE, forever frame, long polling10
- WebSockets9
- JSON7
- Simple6
- Open source4
- Cool4
- Ease of use1
- Requires jQuery1
- Expertise hard to get1
- Weak iOS and Android support1
related SignalR posts
- Fastest pub-sub system out there19
- Rock solid13
- Easy to grasp10
- Easy, Fast, Secure2
- Light-weight1
- No Persistence1
related NATS posts
- Massively scalable & easy to use33
- Easy setup24
- Great support18
- Reliable18
- Flexible to integrate to custom applications14
- High-Performance13
- 99.999% availability guarantees12
- Sockets at Scale12
- Multiplexing12
- High-Reliability11
- Scalability7
- High-Availability5
- 70+ SDKs5
- Azure Add-on4
- Security4
- Presence3
- Heroku Add-on3
- Flexible3
- Easy to setup3
- Data Sync2
- AngularJS Adapter2
- PhoneGap Plugin2
- Server-Side Cache2
- Free Plan2
- Support2
- Analytics2
- Data Streams2
- Easy setup and very reliable1
- Real time and easy to use.1
- High cost, going up more in Summer '151
- Cool1
- 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?