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?
AblyFor 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.
FirebaseI 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.
AblyHello 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
Pros of Firebase
- Realtime backend made easy361
- Fast and responsive264
- Easy setup234
- Real-time207
- JSON186
- Free128
- Backed by google121
- Angular adaptor81
- Reliable63
- Great customer support36
- Great documentation26
- Real-time synchronization23
- Mobile friendly20
- Rapid prototyping17
- Great security12
- Automatic scaling11
- Freakingly awesome10
- Chat8
- Angularfire is an amazing addition!8
- Super fast development8
- Awesome next-gen backend6
- Ios adaptor6
- Built in user auth/oauth5
- Firebase hosting5
- Speed of light4
- Very easy to use4
- It's made development super fast3
- Great3
- Brilliant for startups3
- Great all-round functionality2
- Low battery consumption2
- I can quickly create static web apps with no backend2
- The concurrent updates create a great experience2
- JS Offline and Sync suport2
- Faster workflow1
- Large1
- Serverless1
- .net1
- Free SSL1
- Good Free Limits1
- Push notification1
- Easy to use1
- Easy Reactjs integration1
Pros of PubNub
- Massively scalable & easy to use35
- Easy setup25
- Reliable20
- Great support19
- Flexible to integrate to custom applications14
- Sockets at Scale13
- High-Performance13
- 99.999% availability guarantees13
- Multiplexing12
- High-Reliability12
- Scalability7
- 70+ SDKs5
- High-Availability5
- Security4
- Azure Add-on4
- Heroku Add-on3
- Easy to setup3
- Flexible3
- Presence3
- Analytics2
- Free Plan2
- Server-Side Cache2
- PhoneGap Plugin2
- AngularJS Adapter2
- Data Sync2
- Data Streams2
- 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
Pros of Socket.IO
- Real-time214
- Event-based communication143
- Node.js142
- Open source102
- WebSockets102
- Binary streaming26
- No internet dependency22
- Fallback to polling if WebSockets not supported9
- Large community8
- Ease of access and setup5
- Push notification4
Sign up to add or upvote prosMake informed product decisions
Cons of Firebase
- Can become expensive29
- No open source, you depend on external company15
- Scalability is not infinite15
- Not Flexible Enough9
- Cant filter queries5
- Very unstable server3
- No Relational Data2
- Too many errors2
- No offline sync1
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
Sign up to add or upvote consMake informed product decisions
What is Firebase?
What is PubNub?
What is Socket.IO?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Firebase?
What companies use PubNub?
What companies use Socket.IO?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with PubNub?
What tools integrate with Socket.IO?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+7
+4
+5