Firehose.io vs PubNub: What are the differences?
Firehose.io and PubNub belong to "Realtime Backend / API" category of the tech stack.
Some of the features offered by Firehose.io are:
- Firehose embraces RESTful design prinicpals and consequently works great with any library that speaks HTTP
- Integrates with Backbone.js and Ember.js
- Hook it into an ORM, like ActiveRecord
On the other hand, PubNub provides the following key features:
- Data Push - Establish and maintain persistent socket connections to any device (mobile, browser, desktop and server) and push data to global audiences in less than ¼ of a second
- Presence - Automatically detect when users enter or leave your app and whether machines are online
What is Firehose.io?
What is PubNub?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Firehose.io?
What are the cons of using PubNub?
Sign up to get full access to all the companiesMake informed product decisions
I recently used PubNub to implement a realtime leaderboard into my Unity game. It was easy and straight forward to get up and running. I choose Pubnub because they had a Unity SDK and an example project which showed me how to use it. I downloaded the example project and tweaked it to fit my game.
In their documentation I found good information about what I needed to know. Also, their support is very helpful when you have questions.
I used PubNub because we needed a real time server for our product. Even though we selected a fixed amount paid version, the amount they charged was incredibly high, 8x of the fixed amount. We could not understand how did they do the calculation and there is no easy way of understanding it. Regarding to the analytics they have, we spent millions of messages with few hundred active users.
Then for the second month we tried to change our architecture to decrease the messages but nothing changed. Then we wanted to get some support from them. We arranged a meeting and the person who joined the meeting didn't even have permissions to see our usage, so it was waste of time. Then they arranged another meeting WEEKS after which didn't solve anything either. As a result, we stopped using it and implemented our own simple pub-sub server.
I was building up an Alexa Skill in which user orders a meal and its notification gets to the system of the restaurant and gets displayed which was implemented using PubNub which helped me a lot in getting real time updates and notifications. I used simple publish and subscribe module to implement it which resolved a major challenge. The 5 to 6 lines of python code get my every single chain working with notifications. Thanking PubNub for this major support for solving the challenge.
I use PubNub because is simple and easy I use on Chat app this service has stable, cheap and userfriendly. The admin interface is very easy to understand and you will find a lot of tutorials and learning at their website. Pubnub comes with my highest recommendation for anyone working with apps with chat, push notifications and other realtime data.
PubNub is my goto solution for when I want to use sockets at scale. They have redundant data centers in 14 regions with 99.999% SLA allowing me to build realtime apps for any platform. Also Stephen (PubNub CTO) is Awesome!
Using websockets is something, scaling a message pipeline to thousands of concurrent connections is something else.
I trust PubNub with what it does best, and use it as zerotoherojs.com ’s messaging pipeline.
With PubNub, I have one less problem to think about.