Alternatives to Google Cloud Pub/Sub logo

Alternatives to Google Cloud Pub/Sub

Firebase, Socket.IO, Pusher, SignalR, and PubNub are the most popular alternatives and competitors to Google Cloud Pub/Sub.
216
103
+ 1
1

What is Google Cloud Pub/Sub and what are its top alternatives?

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鈥檚 flexibility to decouple systems and components hosted on Google Cloud Platform or elsewhere on the Internet.
Google Cloud Pub/Sub is a tool in the Realtime Backend / API category of a tech stack.

Google Cloud Pub/Sub alternatives & related posts

related Firebase posts

fontumi
fontumi
Firebase
Firebase
Node.js
Node.js
FeathersJS
FeathersJS
Vue.js
Vue.js
Google Compute Engine
Google Compute Engine
Dialogflow
Dialogflow
Cloud Firestore
Cloud Firestore
Git
Git
GitHub
GitHub
Visual Studio Code
Visual Studio Code

Fontumi focuses on the development of telecommunications solutions. We have opted for technologies that allow agile development and great scalability.

Firebase and Node.js + FeathersJS are technologies that we have used on the server side. Vue.js is our main framework for clients.

Our latest products launched have been focused on the integration of AI systems for enriched conversations. Google Compute Engine , along with Dialogflow and Cloud Firestore have been important tools for this work.

Git + GitHub + Visual Studio Code is a killer stack.

See more
Aliadoc Team
Aliadoc Team
at aliadoc.com | 5 upvotes 230.5K views
atAliadocAliadoc
React
React
Create React App
Create React App
CloudFlare
CloudFlare
Firebase
Firebase
Cloud Functions for Firebase
Cloud Functions for Firebase
Google App Engine
Google App Engine
Google Cloud Storage
Google Cloud Storage
Serverless
Serverless
Visual Studio Code
Visual Studio Code
Bitbucket
Bitbucket
#Aliadoc

In #Aliadoc, we're exploring the crowdfunding option to get traction before launch. We are building a SaaS platform for website design customization.

For the Admin UI and website editor we use React and we're currently transitioning from a Create React App setup to a custom one because our needs have become more specific. We use CloudFlare as much as possible, it's a great service.

For routing dynamic resources and proxy tasks to feed websites to the editor we leverage CloudFlare Workers for improved responsiveness. We use Firebase for our hosting needs and user authentication while also using several Cloud Functions for Firebase to interact with other services along with Google App Engine and Google Cloud Storage, but also the Real Time Database is on the radar for collaborative website editing.

We generally hate configuration but honestly because of the stage of our project we lack resources for doing heavy sysops work. So we are basically just relying on Serverless technologies as much as we can to do all server side processing.

Visual Studio Code definitively makes programming a much easier and enjoyable task, we just love it. We combine it with Bitbucket for our source code control needs.

See more

related Socket.IO posts

across_the_grid
across_the_grid
Full-stack web developer at Capmo GmbH | 10 upvotes 85.7K views
Socket.IO
Socket.IO
Node.js
Node.js
ExpressJS
ExpressJS

I use Socket.IO because the application has 2 frontend clients, which need to communicate in real-time. The backend-server handles the communication between these two clients via websockets. Socket.io is very easy to set up in Node.js and ExpressJS.

In the research project, the 1st client shows panoramic videos in a so called cave system (it is the VR setup of our research lab, which consists of three big screens, which are specially arranged, so the user experience the videos more immersive), the 2nd client controls the videos/locations of the 1st client.

See more
React
React
Redux
Redux
FeathersJS
FeathersJS
HTML5
HTML5
JavaScript
JavaScript
MongoDB
MongoDB
Redis
Redis
Socket.IO
Socket.IO
ES6
ES6

I have always been interested in building a real-time multiplayer game engine that could be massively scalable, and recently I decided to start working on a MMO version of the classic "snake" game. I wanted the entire #Stack to be based on ES6 JavaScript so for the #Backend I chose to use FeathersJS with MongoDB for game/user data storage, Redis for distributed mutex and pub/sub, and Socket.IO for real-time communication. For the #Frontend I used React with Redux.js, the FeathersJS client as well as HTML5 canvas to render the view.

See more

related Pusher posts

Pusher
Pusher
PubNub
PubNub
Google Cloud Pub/Sub
Google Cloud Pub/Sub

Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?

See more
SignalR logo

SignalR

177
186
51
177
186
+ 1
51
A new library for ASP.NET developers that makes developing real-time web functionality easy.
SignalR logo
SignalR
VS
Google Cloud Pub/Sub logo
Google Cloud Pub/Sub

related PubNub posts

Pusher
Pusher
PubNub
PubNub
Google Cloud Pub/Sub
Google Cloud Pub/Sub

Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?

See more
NATS logo

NATS

103
102
36
103
102
+ 1
36
Lightweight publish-subscribe & distributed queueing messaging system
NATS logo
NATS
VS
Google Cloud Pub/Sub logo
Google Cloud Pub/Sub
WCF logo

WCF

52
25
0
52
25
+ 1
0
A runtime and a set of APIs for building connected, service-oriented applications
    Be the first to leave a pro
    WCF logo
    WCF
    VS
    Google Cloud Pub/Sub logo
    Google Cloud Pub/Sub
    deepstream.io logo

    deepstream.io

    28
    59
    36
    28
    59
    + 1
    36
    A scalable server for realtime webapps
    deepstream.io logo
    deepstream.io
    VS
    Google Cloud Pub/Sub logo
    Google Cloud Pub/Sub
    Faye logo

    Faye

    23
    20
    23
    23
    20
    + 1
    23
    Simple pub/sub messaging for the web
    Faye logo
    Faye
    VS
    Google Cloud Pub/Sub logo
    Google Cloud Pub/Sub
    Pulsar logo

    Pulsar

    14
    28
    2
    14
    28
    + 1
    2
    Distributed solution providing messaging and queuing for streaming data
    Pulsar logo
    Pulsar
    VS
    Google Cloud Pub/Sub logo
    Google Cloud Pub/Sub

    related Pulsar posts

    Marc Bollinger
    Marc Bollinger
    Infra & Data Eng Manager at Thumbtack | 4 upvotes 133.2K views
    atLumosityLumosity
    Node.js
    Node.js
    Ruby
    Ruby
    Kafka
    Kafka
    Scala
    Scala
    Apache Storm
    Apache Storm
    Heron
    Heron
    Redis
    Redis
    Pulsar
    Pulsar

    Lumosity is home to the world's largest cognitive training database, a responsibility we take seriously. For most of the company's history, our analysis of user behavior and training data has been powered by an event stream--first a simple Node.js pub/sub app, then a heavyweight Ruby app with stronger durability. Both supported decent throughput and latency, but they lacked some major features supported by existing open-source alternatives: replaying existing messages (also lacking in most message queue-based solutions), scaling out many different readers for the same stream, the ability to leverage existing solutions for reading and writing, and possibly most importantly: the ability to hire someone externally who already had expertise.

    We ultimately migrated to Kafka in early- to mid-2016, citing both industry trends in companies we'd talked to with similar durability and throughput needs, the extremely strong documentation and community. We pored over Kyle Kingsbury's Jepsen post (https://aphyr.com/posts/293-jepsen-Kafka), as well as Jay Kreps' follow-up (http://blog.empathybox.com/post/62279088548/a-few-notes-on-kafka-and-jepsen), talked at length with Confluent folks and community members, and still wound up running parallel systems for quite a long time, but ultimately, we've been very, very happy. Understanding the internals and proper levers takes some commitment, but it's taken very little maintenance once configured. Since then, the Confluent Platform community has grown and grown; we've gone from doing most development using custom Scala consumers and producers to being 60/40 Kafka Streams/Connects.

    We originally looked into Storm / Heron , and we'd moved on from Redis pub/sub. Heron looks great, but we already had a programming model across services that was more akin to consuming a message consumers than required a topology of bolts, etc. Heron also had just come out while we were starting to migrate things, and the community momentum and direction of Kafka felt more substantial than the older Storm. If we were to start the process over again today, we might check out Pulsar , although the ecosystem is much younger.

    To find out more, read our 2017 engineering blog post about the migration!

    See more
    Horizon logo

    Horizon

    13
    33
    0
    13
    33
    + 1
    0
    A realtime, open-source JavaScript back end from RethinkDB
      Be the first to leave a pro
      Horizon logo
      Horizon
      VS
      Google Cloud Pub/Sub logo
      Google Cloud Pub/Sub
      ws logo

      ws

      13
      15
      0
      13
      15
      + 1
      0
      A Node.js WebSocket library
        Be the first to leave a pro
        ws logo
        ws
        VS
        Google Cloud Pub/Sub logo
        Google Cloud Pub/Sub
        Gun logo

        Gun

        10
        40
        0
        10
        40
        + 1
        0
        Self-hosted Firebase.
        Gun logo
        Gun
        VS
        Google Cloud Pub/Sub logo
        Google Cloud Pub/Sub
        LeanCloud logo

        LeanCloud

        8
        6
        0
        8
        6
        + 1
        0
        Leading serverless cloud service
          Be the first to leave a pro
          LeanCloud logo
          LeanCloud
          VS
          Google Cloud Pub/Sub logo
          Google Cloud Pub/Sub
          Telepat logo

          Telepat

          8
          32
          0
          8
          32
          + 1
          0
          Real time data synchronization platform for modern API driven web&mobile apps
            Be the first to leave a pro
            Telepat logo
            Telepat
            VS
            Google Cloud Pub/Sub logo
            Google Cloud Pub/Sub
            8base logo

            8base

            6
            8
            0
            6
            8
            + 1
            0
            A fully-managed, cloud-based data and serverless compute service exposed through a GraphQL API.
              Be the first to leave a pro
              8base logo
              8base
              VS
              Google Cloud Pub/Sub logo
              Google Cloud Pub/Sub
              Pushpin logo

              Pushpin

              6
              27
              2
              6
              27
              + 1
              2
              Reverse proxy for realtime web services
              Pushpin logo
              Pushpin
              VS
              Google Cloud Pub/Sub logo
              Google Cloud Pub/Sub