Need advice about which tool to choose?Ask the StackShare community!
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
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 easy367
- Fast and responsive268
- Easy setup240
- Real-time212
- JSON188
- Free132
- Backed by google126
- Angular adaptor82
- Reliable67
- Great customer support35
- Great documentation30
- Real-time synchronization25
- Mobile friendly21
- Rapid prototyping18
- Great security14
- Automatic scaling12
- Freakingly awesome11
- Chat8
- Angularfire is an amazing addition!8
- Super fast development8
- Firebase hosting6
- Awesome next-gen backend6
- Ios adaptor6
- Built in user auth/oauth6
- Speed of light4
- Very easy to use4
- Great3
- Brilliant for startups3
- It's made development super fast3
- Push notification2
- Free hosting2
- Free authentication solution2
- Cloud functions2
- JS Offline and Sync suport2
- 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 to use1
- Easy Reactjs integration1
- Free SSL1
- Faster workflow1
- Google's support1
- Simple and easy1
- CDN & cache out of the box1
- Large1
- .net1
- Serverless1
- Good Free Limits1
Pros of PubNub
- Massively scalable & easy to use36
- Easy setup25
- Reliable20
- Great support19
- Flexible to integrate to custom applications14
- 99.999% availability guarantees13
- Sockets at Scale13
- High-Performance13
- Multiplexing12
- High-Reliability12
- Scalability7
- 70+ SDKs5
- High-Availability5
- Azure Add-on4
- Security4
- Heroku Add-on3
- Presence3
- Easy to setup3
- Flexible3
- Server-Side Cache2
- Free Plan2
- Support2
- AngularJS Adapter2
- PhoneGap Plugin2
- Data Sync2
- Data Streams2
- Analytics2
- Angular 2+ integration1
- Easy integration with iOS apps1
- Easy setup and very reliable1
- High cost, going up more in Summer '151
- Cool1
- Documentation, easy to use, great people/service1
- CTO stephen also is A++++++1
- Real time and easy to use.1
- Cdsd1
Pros of Socket.IO
- Real-time214
- 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
Sign up to add or upvote prosMake informed product decisions
Cons of Firebase
- Can become expensive31
- No open source, you depend on external company15
- Scalability is not infinite15
- Not Flexible Enough9
- Cant filter queries6
- No Relational Data3
- Very unstable server3
- Too many errors2
- No offline sync2
Cons of PubNub
- Costly1
Cons of Socket.IO
- Bad documentation11
- Githubs that complement it are mostly deprecated4
- Doesn't work on React Native3
- Websocket Errors2
- Small community2