deepstream.io vs Firebase vs Socket.IO

deepstream.io
deepstream.io

25
1
36
Firebase
Firebase

5.8K
242
1.7K
Socket.IO
Socket.IO

2.8K
50
669
- No public GitHub repository available -

What is deepstream.io?

Scalable Server for Realtime Web Apps with JSON structures that can be read, manipulated and listened to, messages that can be sent to one or more subscribers, and request response workflows, between two clients or servers.

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 Socket.IO?

Socket.IO enables real-time bidirectional event-based communication. It works on every platform, browser or device, focusing equally on reliability and speed.

Want advice about which of these to choose?Ask the StackShare community!

Why do developers choose deepstream.io?
Why do developers choose Firebase?
Why do developers choose Socket.IO?
What are the cons of using deepstream.io?
What are the cons of using Firebase?
What are the cons of using Socket.IO?
    Be the first to leave a con
    What companies use deepstream.io?
    What companies use Firebase?
    What companies use Socket.IO?
    What are some alternatives to deepstream.io, Firebase, and Socket.IO?
    Pusher
    Pusher is the category leader in delightful APIs for app developers building communication and collaboration features.
    Google Cloud Pub/Sub
    Cloud Pub/Sub is a fully-managed real-time messaging service that allows you to send and receive messages between independent applications. You can leverage Cloud Pub/Sub’s flexibility to decouple systems and components hosted on Google Cloud Platform or elsewhere on the Internet.
    SignalR
    SignalR allows bi-directional communication between server and client. Servers can now push content to connected clients instantly as it becomes available. SignalR supports Web Sockets, and falls back to other compatible techniques for older browsers. SignalR includes APIs for connection management (for instance, connect and disconnect events), grouping connections, and authorization.
    PubNub
    PubNub makes it easy for you to add real-time capabilities to your apps, without worrying about the infrastructure. Build apps that allow your users to engage in real-time across mobile, browser, desktop and server.
    NATS
    Unlike traditional enterprise messaging systems, NATS has an always-on dial tone that does whatever it takes to remain available. This forms a great base for building modern, reliable, and scalable cloud and distributed systems.
    See all alternatives
    What tools integrate with deepstream.io?
    What tools integrate with Firebase?
    What tools integrate with Socket.IO?
      No integrations found
        No integrations found
        Decisions about deepstream.io, Firebase, and Socket.IO
        No stack decisions found
        Interest over time
        Reviews of deepstream.io, Firebase, and Socket.IO
        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 deepstream.io, Firebase, and Socket.IO
        Avatar of Tony Manso
        Tony Manso uses Socket.IOSocket.IO

        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.

        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 Trello
        Trello uses Socket.IOSocket.IO

        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.

        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 Kent Steiner
        Kent Steiner uses Socket.IOSocket.IO

        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.

        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 Andrew Gatenby
        Andrew Gatenby uses Socket.IOSocket.IO

        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.

        Avatar of AngeloR
        AngeloR uses Socket.IOSocket.IO

        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.

        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.

        How much does deepstream.io cost?
        How much does Firebase cost?
        How much does Socket.IO cost?
        Pricing unavailable
        Pricing unavailable
        News about deepstream.io
        More news
        News about Socket.IO
        More news