Need advice about which tool to choose?Ask the StackShare community!
Faye vs Firebase: What are the differences?
Introduction
Faye and Firebase are both real-time data synchronization technologies commonly used in web development. Despite having similar functionalities, there are key differences between the two that developers should consider before choosing one over the other.
Data Storage: Firebase is a cloud-based platform that provides real-time database storage for web and mobile applications, allowing developers to store and sync data in real time. In contrast, Faye is a messaging system that primarily focuses on real-time client-server communication through the use of pub/sub messaging patterns.
Offline Support: Firebase offers robust offline support by caching data locally on the device, allowing users to access and interact with the application even when they are offline. On the other hand, Faye does not natively support offline capabilities, making it less suitable for applications that require persistent data access in offline scenarios.
Scalability: Firebase is known for its horizontal scalability, making it suitable for applications that may experience rapid growth in user base or data volume. Faye, while scalable, may require additional configuration and setup to achieve the same level of scalability as Firebase.
Authentication: Firebase provides built-in authentication mechanisms that allow developers to easily implement user authentication and authorization in their applications. In contrast, Faye does not offer native authentication features, requiring developers to implement custom authentication solutions for securing their applications.
Real-time Querying: Firebase allows for real-time querying of data, enabling developers to retrieve and update data in real time without the need for manual refreshes. Faye, on the other hand, primarily focuses on real-time messaging and may require additional implementation for real-time querying capabilities.
Cost: Firebase offers a freemium pricing model with a generous free tier for small to medium-sized applications, making it cost-effective for startups and individual developers. Faye, being an open-source technology, is more cost-effective in terms of licensing but may require more resources for maintenance and support.
In Summary, Faye and Firebase differ in terms of data storage, offline support, scalability, authentication, real-time querying, and cost efficiency. Developers should carefully consider these factors before choosing the most suitable technology for their projects.
We (my team) are building an App where we want to have Bi-directional texting, Single Directional Picture, and audio transfer.
We are building all this using Flutter.
There will essentially be 3 apps, 2 Mobile-based (Android and iOS) and 1 Microsoft Based. We've built up most of the code already, and made a few major mistakes but fixed it(namely had no proper state management).
How things will work:
Person A has a Mobile app 1, Person A presses a button that sends a "communication request" into a Pool of requests. Person B on Desktop App chooses a "communication request" from the pool, and engages in Bi-directional texting with Person A. Person B also opens communication with Person C who is on Mobile app 2, and they engage in Bi-directional texting. Person C will be notified of communication requests through Push Notifications.
So far we've been using Socket.IO, however, I'm starting to think that's not the best.
A problem we've encountered so far is that Person A(Mobile App 1 User), is the person who sends a "communication request" into the "Communication Pool". The Mobile App 1 User, can "cancel" the communication at any point in time. When they do that, I would like for a notification to be sent to Person B, the Desktop User, For them to pick up another communication request.
I am not sure how this should be done however, should it be done in the Back-end, then how does the Front-end get notified of the change?
Any advice on which to choose?
It's so simple when you use Firebase to manage the requests just make new field to the request for example callstate with values like "requesting" "incall" "cancelled" and both A and B can update this field.
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.
I would recommend looking hard into Firebase for this project, especially if you do not have dedicated full-stack or backend members on your team.
The real time database, as you mentioned, is a great option, but I would also look into Firestore. Similar to RTDB, it adds more functions and some cool methods as well. Also, another great thing about Firebase is you have easy access to storage and dead simple auth as well.
Node.js Express MongoDB Socket.IO and Apollo are great technologies as well, and may be the better option if you do not wish to cede as much control to third parties in your application.
Overall, I say if you wish to focus more time developing your React application instead of other parts of your stack, Firebase is a great way to do that.
Hello Noam 👋,
I suggest taking a look at Ably, it has all the realtime features you need and the platform is designed to guarantee critical functionality at scale.
Here is an in depth comparison between Ably and Firebase
Hey Noam,
I would recommend you to take a look into 8base. It has features you've requested, also relation database and GraphQL API which will help you to develop rapidly.
Thanks, Ilya
The start-up guides, tutorials and documentation in general for Firebase are pretty outstanding.
There is 1GB database storage for the free tier as compared to Supabase's 500MB. Not that I think there is anything wrong with Supabase, I intend to try it out someday.
Also if you are doing any sort of personal front-end project, even using a free cluster from MongoDB can be a lot of work and setup, with Firebase (specifically Fire store and Google Authenticator) the implementation of BaaS is quite easy to get up and running.
It's pretty easy to understand the Fires store security rules as well, and if you ever have a hard time trying to figure something out, there is good community support and YouTube tutorials for most topics.
Pros of Faye
- Simple6
- Open source5
- Node.js5
- Real-time2
- Scalable2
- Ruby (EventMachine)2
- BAYEUX Protocol (not proprietary)2
Pros of Firebase
- Realtime backend made easy371
- Fast and responsive270
- Easy setup242
- Real-time215
- JSON191
- Free134
- Backed by google128
- Angular adaptor83
- Reliable68
- Great customer support36
- Great documentation32
- Real-time synchronization25
- Mobile friendly21
- Rapid prototyping19
- Great security14
- Automatic scaling12
- Freakingly awesome11
- Super fast development8
- Angularfire is an amazing addition!8
- Chat8
- Firebase hosting6
- Built in user auth/oauth6
- Awesome next-gen backend6
- Ios adaptor6
- Speed of light4
- Very easy to use4
- Great3
- It's made development super fast3
- Brilliant for startups3
- Free hosting2
- Cloud functions2
- JS Offline and Sync suport2
- Low battery consumption2
- .net2
- The concurrent updates create a great experience2
- Push notification2
- I can quickly create static web apps with no backend2
- Great all-round functionality2
- Free authentication solution2
- Easy Reactjs integration1
- Google's support1
- Free SSL1
- CDN & cache out of the box1
- Easy to use1
- Large1
- Faster workflow1
- Serverless1
- Good Free Limits1
- Simple and easy1
Sign up to add or upvote prosMake informed product decisions
Cons of Faye
Cons of Firebase
- 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
Sign up to add or upvote consMake informed product decisions
What is Faye?
What is Firebase?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Faye?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Faye?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+5