Firebase vs Pusher vs SocketCluster

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Firebase
Firebase

9.6K
7.5K
+ 1
1.8K
Pusher
Pusher

389
354
+ 1
218
SocketCluster
SocketCluster

29
51
+ 1
40
- No public GitHub repository available -
- No public GitHub repository available -

What is Firebase?

Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds.

What is Pusher?

Pusher is the category leader in delightful APIs for app developers building communication and collaboration features.

What is SocketCluster?

SocketCluster is a fast, highly scalable HTTP + realtime server engine which lets you build multi-process realtime servers that make use of all CPU cores on a machine/instance. It removes the limitations of having to run your Node.js server as a single thread and makes your backend resilient by automatically recovering from worker crashes and aggregating errors into a central log.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Firebase?
Why do developers choose Pusher?
Why do developers choose SocketCluster?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
      Be the first to leave a con

      Sign up to add, upvote and see more consMake informed product decisions

      What companies use Firebase?
      What companies use Pusher?
      What companies use SocketCluster?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Firebase?
      What tools integrate with Pusher?
      What tools integrate with SocketCluster?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Firebase, Pusher, and SocketCluster?
      Parse
      With Parse, you can add a scalable and powerful backend in minutes and launch a full-featured app in record time without ever worrying about server management. We offer push notifications, social integration, data storage, and the ability to add rich custom logic to your app’s backend with Cloud Code.
      MongoDB
      MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.
      Auth0
      A set of unified APIs and tools that instantly enables Single Sign On and user management to all your applications.
      Heroku
      Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.
      Realm
      The Realm Mobile Platform is a next-generation data layer for applications. Realm is reactive, concurrent, and lightweight, allowing you to work with live, native objects.
      See all alternatives
      Decisions about Firebase, Pusher, and SocketCluster
      Tomáš Pustelník
      Tomáš Pustelník
      Firebase
      Firebase

      We use Firebase at work (and I use it for my personal projects) for several reasons:

      1) it is not just real-time DB with subscriptions but a lot more (storage for files, push notifications for mobile, cloud functions etc.) so it allows to build quite a robust solutions, but still possible to use just a minimal set of what you need

      2) In most cases it's pretty cheap (unless you messed up you DB structure, reads/writes etc. - could be problem for a lot of traffic - so in such a case ready pricing and related guides properly), for side projects basically free.

      3) offers free hosting with SSL certificates for static files

      4) you can bootstrap functional prototype really quick and for the production, you do not need to worry about scaling.

      See more
      Jared Wuliger
      Jared Wuliger
      Contractor at Insight Global · | 9 upvotes · 65.6K views
      Firebase
      Firebase

      I started using Firebase over 5 years ago because of the 'real-time' nature. I originally used to use Real Time Database, but now I use Cloud Firestore. I recommend using the Google Firebase PaaS to quickly develop or prototype small to enterprise level web/mobile applications. Since Google purchased Firebase, it has exploded and it growing rapidly. I also find some level of comfort that it is Backed by Google.

      See more
      Interest over time
      Reviews of Firebase, Pusher, and SocketCluster
      Review ofFirebaseFirebase

      Firebase is great, cheap and very flexible. Their docs are very helpful and so is the customer support, but the one thing that is so awesome about firebase is that everything is done in realtime!

      Review ofFirebaseFirebase

      We were looking for a solution to find out about all the errors our customers experienced but never informed us about.

      How developers use Firebase, Pusher, and SocketCluster
      Avatar of Instacart
      Instacart uses FirebaseFirebase

      We use it for a few things. We use it internally for a few dashboards because it’s actually really nice to have real-time dashboard data with Firebase. We also use it extensively for live order updating. For example, when a shopper is picking your items, you'll be able to go on your order screen. There will be live showing like found or not found or whatever. You'll have live position updating of your shopper on the map. You will have live information of the status of the order like “Nicole is now picking up your order,” and all these kind of things, so you don’t have to reload the page or pull or anything. Just live updates happen natively through Firebase API, which is nice.

      Avatar of Instacart
      Instacart uses FirebaseFirebase

      We use it for a few things. We use it internally for a few dashboards because it’s actually really nice to have real-time dashboard data with Firebase. We also use it extensively for live order updating. For example, when a shopper is picking your items, you'll be able to go on your order screen. There will be live showing like found or not found or whatever. You'll have live position updating of your shopper on the map. You will have live information of the status of the order like “Nicole is now picking up your order,” and all these kind of things, so you don’t have to reload the page or pull or anything. Just live updates happen natively through Firebase API, which is nice.

      Avatar of Nathan Heffley
      Nathan Heffley uses PusherPusher

      In the original prototype all the communication was handled by a backend server. Each client connected directly to the server using the socket.io library. This quickly proved to be messy and unreliable, especially on the cheap server being used to host it.

      Websockets proved to be a little more reliable, but still just as messy and not all browsers support them. That's when the project was switched over to use Pusher. Using Pusher has allowed all but the initial connection code to be off-loaded onto the client. Now instead of communicating through a self-hosted server, clients can communicate pretty much peer-to-peer over Pusher.

      Avatar of ttandon
      ttandon uses FirebaseFirebase

      Used for storing results of users (malaria predictions) and displaying to user in the app. Although the realtime aspect wasn't huge in this project, it was much quicker to push data elements for each user as firebase elements since they were purely numerical and very small. And again, the idea of familiarity - I've worked with Firebase at previous hackathons, so no need to spend time going through docs, just straight to the coding.

      Avatar of NewCraft
      NewCraft uses FirebaseFirebase

      Firebase let's us iterate quickly. We've used the Realtime Database to build rich UX features– like push notifications– fast. Likewise, Firebase Authentication and Cloud Functions save us from having to rebuild redundant server infrastructure. Even though Firebase can get pricey, we've saved money in developer time.

      Avatar of Addo
      Addo uses FirebaseFirebase

      Still in development, but we will soon (January 2016) be releasing a version that uses Firebase to keep the front end up to date in real time. Certain data are synchronised across RDS and Firebase to optimize the user experience.

      Avatar of Jewel Mahanta
      Jewel Mahanta uses PusherPusher

      Pusher is used to send update notification whenever Lapzbot joins a server.

      Avatar of Vamsi Krishna
      Vamsi Krishna uses PusherPusher

      Push real-time updates

      How much does Firebase cost?
      How much does Pusher cost?
      How much does SocketCluster cost?
      Pricing unavailable
      News about SocketCluster
      More news