Need advice about which tool to choose?Ask the StackShare community!
Firebase vs PubNub: What are the differences?
Introduction
Firebase and PubNub are two popular platforms used for building real-time applications. While both offer real-time messaging and push notifications, there are key differences between the two that make each platform unique. Let's explore some of these differences below.
Scalability: Firebase is known for its scalability as it is built on Google Cloud Platform, which provides robust infrastructure to handle heavy loads and large user bases. It can automatically scale to meet the needs of apps that experience significant growth. On the other hand, PubNub also offers scalability but doesn't have the same level of infrastructure as Firebase since it is a separate platform.
Data Synchronization: Firebase provides a real-time database that can automatically synchronize data across multiple devices. This means that any changes made on one device will be immediately reflected on all other connected devices. PubNub also offers data synchronization, but it requires more manual implementation compared to Firebase.
Authentication: Firebase offers built-in authentication services, allowing developers to easily add user authentication to their apps. It supports various authentication methods like email/password, social logins, and even custom authentication. PubNub, on the other hand, doesn't provide native authentication features. Developers would need to implement their own authentication system or integrate with another service.
Serverless Backend: Firebase provides a serverless backend, allowing developers to focus more on the frontend development without worrying about managing servers or infrastructure. It offers features like cloud functions and cloud storage, making it easier to build serverless architectures. PubNub, on the other hand, is primarily focused on real-time messaging and doesn't provide the same level of serverless backend capabilities as Firebase.
Real-time Functionality: Both Firebase and PubNub excel in providing real-time functionality. However, Firebase is more suited for apps that require real-time updates within a confined user base, such as chat apps or collaborative tools. PubNub, on the other hand, is designed for large-scale, real-time applications that need to handle high volumes of messages and users, making it a better choice for applications that require massive scalability.
Integrations: Firebase offers seamless integrations with other Google Cloud Platform services, such as Cloud Firestore for more advanced database needs, Cloud Messaging for push notifications, and Cloud Functions for serverless backend logic. PubNub, on the other hand, offers integrations with a variety of third-party services including AWS, Azure, and Google Cloud, providing developers with more flexibility to integrate with their preferred services.
In summary, Firebase provides scalability, easy data synchronization, built-in authentication, serverless backend, real-time capabilities for confined user bases, and seamless integrations with other Google Cloud services. PubNub, on the other hand, offers scalability, data synchronization with manual implementation, requires custom authentication, focused on real-time messaging, better suited for large-scale applications, and offers integrations with various third-party services.
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.
I am building an IoT application that will utilize connected air quality sensors to provide real-time indoor air quality in offices. I want to be able to share this data with a few different databases, etc.
Wondering if anyone has any advice on which real-time streaming API would be best for this sort of application, or even how I should think about it?
For IoT, we support MQTT along with websockets and SSE. The pattern you're suggesting that involves harvesting data from devices and soaking into a database is easy to achieve with one of the Ably integrations (Serverless functions/webhook) . Here are some tutorials to do things like this: https://ably.com/tutorials/reactor-event-zapier#step2-mqtt-ably
We use Pusher at www.justlearn.com. It works fine. When you reach more users, Pusher gets expensive. We use Pusher for live chat between users. Their software is easy to use. We have had issues with auth on Pusher.
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 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
Pros of PubNub
- Massively scalable & easy to use36
- Easy setup25
- Reliable20
- Great support19
- Flexible to integrate to custom applications14
- Sockets at Scale13
- 99.999% availability guarantees13
- High-Performance13
- High-Reliability12
- Multiplexing12
- Scalability7
- High-Availability5
- 70+ SDKs5
- Security4
- Azure Add-on4
- Heroku Add-on3
- Presence3
- Flexible3
- Easy to setup3
- Data Streams2
- Free Plan2
- Server-Side Cache2
- PhoneGap Plugin2
- AngularJS Adapter2
- Data Sync2
- Analytics2
- Support2
- 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
- Easy integration with iOS apps1
Sign up to add or upvote prosMake informed product decisions
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
Cons of PubNub
- Costly1
Sign up to add or upvote consMake informed product decisions
What is Firebase?
What is PubNub?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with PubNub?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+7
+4
+5