Firebase vs. Socket.IO vs. PubNub

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.

Firebase made it really easy to do two things. 1) Store the shared code developers were sharing 2) Make it real-time simply by including some of their JS libraries. The reason I built CodeShare was to try out Firebase.

All our clients data and settings are stored on fire base which provides real time events for our real time platform. It is great on web, android and iOs

We used Firebase for a second screen experience that aided a 20 Mio. viewer stream. Easy to use and very robust.

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.

Saving and integrating real-time content. Used for login portal and ticket system.

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.

Firebase is used as a simple, realtime backend to store data.

Firebase is the perfect live data backend for my AngularJS projects. The AngularFire API allows a dev to work with synchronized data in a direct and understandable way. Database service of choice.

The glue. No middle tier servers. Rely on Firebase to deliver shared and non shared data for groups. Normalized JSON. Utilize security and hosting to deliver static assets and configuration data.

Application data hosting and administration.

We used firebase to power our backend interface which powers the content on our website as well as a few of our internal tools.

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.

User management

Live chat server

The client sends requests here for the server to answer. Data is encrypted cleared as soon as the client receives the answer to its request.

Our DBaaS and backend. All database operations run trough Firebase and requests/responses arrive in realtime.

Default Google messaging service library since September 2016.

Store data & Auth

Used for POCs when hacking stuff together. Really fast prototyping :-)

Used for hosting and database for a server less implementation.

for hubot's simple database

Used for backend of some Angular projects.

just for the Analytics

Web use Firebase for Mobile app analytics

Push notifications.

Storage to provide current/last values (state)

Firebase is included within our Android- and iOS-App so that we can react and monitor our mobile Applications in a flexible and dynamic fashion. This way we can react on occuring errors fast and reliable.

실시간 백엔드/API

Firebase is used for our live updating prediction graphs and our live data feed API

Backend, Database, Storage, Google Cloud Functions

I use this for backend services for my mobile platform softwares. Its fast growing community is very friendly and it barely takes any time to setup.

I use Firebase for authentication, cloud messaging and the Real-time Firebase Cloud-store. Firebase is easy to use and very secure.

I trusted Firebase since 2014 in other demo apps, real time transact operations over the front end using Angular and AngularFire. Quick to implement.

Mobile Ads and statistics in Xamarin.iOS and Xamarin.Android apps (Bite'It, E-BusinessCard)

A proprietary monolith. We are using openstack instead.

We use it for Analytics data and for Pushing messages to users.

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.

Used in Android Apps

PrometheanTV utilizes the Firebase as our real time database and to provide websocket support to the platform including delivering a realtime overlay experience to connected video clients.

Push notifications, maps and Google login.

We use Firebase Auth for all authentication, Firestore as a client-side database for saving metadata, and Firebase Hosting for all of our application hosting needs.

When choosing between the Firebase version or the GCP version of tools, we tend to pick the Firebase version, as it's often simpler and nicer to work with.

Where we have browser support (recent Chrome, Firefox, and Safari), we make a WebSocket connection so that the server can push changes made by other people down to browsers listening on the appropriate channels. We use a modified version* of the Socket.io client and server libraries that allows us to keep many thousands of open WebSockets on each of our servers at very little cost in terms of CPU or memory usage. So when anything happens to a board you’re watching, that action is published to our server processes and propagated to your watching browser with very minimal latency, usually well under a second.

websocket for realtime communication and map sync

We use socket.io to power Ayedeals business. More specifically for real time analytics.

To communicate between login server and voice / messaging server

Everything on Zube happens in real-time. We hooked Socket into all of our models.

We use socket.io to notify user when long running UI tasks finish.

Live chat server

Real time communication

Used Socket.IO for webRTC application testing.

Sockets used to send latest location.

Socket.io is used for async communication.

Used for sending real-time updates to connected browsers; to give real-time feedback about e.g. messages assigned to you, resolves in the inbox, etc.

Socket.io is used as our current multiplayer engine. The existing engine is very simplistic and only utilizes the websocket+http fallback transports and serves as a generic world/zone/screen grouping mechanism for displaying users to each other.

Socket.IO has a decent community footprint, including integrations with popular JS frameworks, and has fallbacks to maintain an app's services if websockets are not available for some reason. Websockets are an important factor in most of the web-facing apps I build, to provide asynchronous two-way communication between the app and whatever server or data source it is connected to.

I use Socket.IO because using HTTP requests for a real-time multiplayer game just blows! Even with websockets, I had to scrunch the data being transmitted down to a bare minimum, and do some cheap compression tricks so that I can send data in JSON format. Otherwise, I would have to resort to sending binary data. I may end up doing that anyway when the time comes that I need to scale.

How do I use it? Each client opens a socket connection at startup. The server keeps track of these connections, and sends each client the visible portion of the Playfield repeatedly. The clients render this information, while sending requests and commands to the server (join,turn,fire,thrust,bomb,viewport change,etc.) in response to the player's actions. The server uses that to make adjustments to the player's ship on the Playfield.

Socket.IO powered all of the real-time editing capabilities - high performance, easy-to-use, and awesome.

• 웹소켓 클라이언트 Socket.io 를 통해서 간단한 및 알람 기능을 등을 만듬

chat server
raspberry message server

Another one that we're not using, yet. But have realtime data updates within our applications and the central API will be a great bit of functionality that gives our clients more control and keep them informed of changes and updates in their stores, in real time.

No delays!

Socket.IO's websocket fallbacks allow Hndhld to provide an experience for everybody.

P2P signalling

Socket.IO is used for basic websocket capabilities. Used for simple chat applications, and features that require realtime interactions with servers or other clients.

Chat services

Real-time editing, notifications and much more.

Flutter uses PubNub for sending push notifications when the users add new posts to the Flutter Community or leave comments.