Alternatives to Google Cloud Pub/Sub logo

Alternatives to Google Cloud Pub/Sub

Kafka, RabbitMQ, Firebase, Socket.IO, and Pusher are the most popular alternatives and competitors to Google Cloud Pub/Sub.
446
375
+ 1
13

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’s 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.

Top Alternatives to Google Cloud Pub/Sub

  • Kafka
    Kafka

    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design. ...

  • RabbitMQ
    RabbitMQ

    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received. ...

  • Firebase
    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. ...

  • Socket.IO
    Socket.IO

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

  • Pusher
    Pusher

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

  • SignalR
    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. ...

  • NATS
    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. ...

  • PubNub
    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. ...

Google Cloud Pub/Sub alternatives & related posts

Kafka logo

Kafka

18.3K
17.5K
593
Distributed, fault tolerant, high throughput pub-sub messaging system
18.3K
17.5K
+ 1
593
PROS OF KAFKA
  • 125
    High-throughput
  • 119
    Distributed
  • 89
    Scalable
  • 83
    High-Performance
  • 65
    Durable
  • 37
    Publish-Subscribe
  • 19
    Simple-to-use
  • 17
    Open source
  • 11
    Written in Scala and java. Runs on JVM
  • 8
    Message broker + Streaming system
  • 4
    Avro schema integration
  • 4
    Robust
  • 4
    KSQL
  • 2
    Suport Multiple clients
  • 2
    Partioned, replayable log
  • 1
    Flexible
  • 1
    Extremely good parallelism constructs
  • 1
    Simple publisher / multi-subscriber model
  • 1
    Fun
CONS OF KAFKA
  • 29
    Non-Java clients are second-class citizens
  • 27
    Needs Zookeeper
  • 7
    Operational difficulties
  • 2
    Terrible Packaging

related Kafka posts

Eric Colson
Chief Algorithms Officer at Stitch Fix · | 21 upvotes · 2.3M views

The algorithms and data infrastructure at Stitch Fix is housed in #AWS. Data acquisition is split between events flowing through Kafka, and periodic snapshots of PostgreSQL DBs. We store data in an Amazon S3 based data warehouse. Apache Spark on Yarn is our tool of choice for data movement and #ETL. Because our storage layer (s3) is decoupled from our processing layer, we are able to scale our compute environment very elastically. We have several semi-permanent, autoscaling Yarn clusters running to serve our data processing needs. While the bulk of our compute infrastructure is dedicated to algorithmic processing, we also implemented Presto for adhoc queries and dashboards.

Beyond data movement and ETL, most #ML centric jobs (e.g. model training and execution) run in a similarly elastic environment as containers running Python and R code on Amazon EC2 Container Service clusters. The execution of batch jobs on top of ECS is managed by Flotilla, a service we built in house and open sourced (see https://github.com/stitchfix/flotilla-os).

At Stitch Fix, algorithmic integrations are pervasive across the business. We have dozens of data products actively integrated systems. That requires serving layer that is robust, agile, flexible, and allows for self-service. Models produced on Flotilla are packaged for deployment in production using Khan, another framework we've developed internally. Khan provides our data scientists the ability to quickly productionize those models they've developed with open source frameworks in Python 3 (e.g. PyTorch, sklearn), by automatically packaging them as Docker containers and deploying to Amazon ECS. This provides our data scientist a one-click method of getting from their algorithms to production. We then integrate those deployments into a service mesh, which allows us to A/B test various implementations in our product.

For more info:

#DataScience #DataStack #Data

See more
John Kodumal

As we've evolved or added additional infrastructure to our stack, we've biased towards managed services. Most new backing stores are Amazon RDS instances now. We do use self-managed PostgreSQL with TimescaleDB for time-series data—this is made HA with the use of Patroni and Consul.

We also use managed Amazon ElastiCache instances instead of spinning up Amazon EC2 instances to run Redis workloads, as well as shifting to Amazon Kinesis instead of Kafka.

See more
RabbitMQ logo

RabbitMQ

16.9K
14.9K
521
Open source multiprotocol messaging broker
16.9K
14.9K
+ 1
521
PROS OF RABBITMQ
  • 232
    It's fast and it works with good metrics/monitoring
  • 79
    Ease of configuration
  • 58
    I like the admin interface
  • 50
    Easy to set-up and start with
  • 20
    Durable
  • 18
    Intuitive work through python
  • 18
    Standard protocols
  • 10
    Written primarily in Erlang
  • 8
    Simply superb
  • 6
    Completeness of messaging patterns
  • 3
    Scales to 1 million messages per second
  • 3
    Reliable
  • 2
    Better than most traditional queue based message broker
  • 2
    Distributed
  • 2
    Supports AMQP
  • 1
    Inubit Integration
  • 1
    Delayed messages
  • 1
    Supports MQTT
  • 1
    Runs on Open Telecom Platform
  • 1
    High performance
  • 1
    Reliability
  • 1
    Clusterable
  • 1
    Clear documentation with different scripting language
  • 1
    Great ui
  • 1
    Better routing system
CONS OF RABBITMQ
  • 9
    Too complicated cluster/HA config and management
  • 6
    Needs Erlang runtime. Need ops good with Erlang runtime
  • 5
    Configuration must be done first, not by your code
  • 4
    Slow

related RabbitMQ posts

James Cunningham
Operations Engineer at Sentry · | 18 upvotes · 1.4M views
Shared insights
on
CeleryCeleryRabbitMQRabbitMQ
at

As Sentry runs throughout the day, there are about 50 different offline tasks that we execute—anything from “process this event, pretty please” to “send all of these cool people some emails.” There are some that we execute once a day and some that execute thousands per second.

Managing this variety requires a reliably high-throughput message-passing technology. We use Celery's RabbitMQ implementation, and we stumbled upon a great feature called Federation that allows us to partition our task queue across any number of RabbitMQ servers and gives us the confidence that, if any single server gets backlogged, others will pitch in and distribute some of the backlogged tasks to their consumers.

#MessageQueue

See more
Yogesh Bhondekar
Co-Founder at weconnect.chat · | 15 upvotes · 195.3K views

Hi, I am building an enhanced web-conferencing app that will have a voice/video call, live chats, live notifications, live discussions, screen sharing, etc features. Ref: Zoom.

I need advise finalizing the tech stack for this app. I am considering below tech stack:

  • Frontend: React
  • Backend: Node.js
  • Database: MongoDB
  • IAAS: #AWS
  • Containers & Orchestration: Docker / Kubernetes
  • DevOps: GitLab, Terraform
  • Brokers: Redis / RabbitMQ

I need advice at the platform level as to what could be considered to support concurrent video streaming seamlessly.

Also, please suggest what could be a better tech stack for my app?

#SAAS #VideoConferencing #WebAndVideoConferencing #zoom #stack

See more
Firebase logo

Firebase

32.4K
28K
1.9K
The Realtime App Platform
32.4K
28K
+ 1
1.9K
PROS OF FIREBASE
  • 367
    Realtime backend made easy
  • 268
    Fast and responsive
  • 239
    Easy setup
  • 212
    Real-time
  • 188
    JSON
  • 132
    Free
  • 126
    Backed by google
  • 82
    Angular adaptor
  • 67
    Reliable
  • 35
    Great customer support
  • 30
    Great documentation
  • 25
    Real-time synchronization
  • 21
    Mobile friendly
  • 18
    Rapid prototyping
  • 14
    Great security
  • 12
    Automatic scaling
  • 11
    Freakingly awesome
  • 8
    Super fast development
  • 8
    Angularfire is an amazing addition!
  • 8
    Chat
  • 6
    Built in user auth/oauth
  • 6
    Firebase hosting
  • 6
    Ios adaptor
  • 6
    Awesome next-gen backend
  • 4
    Speed of light
  • 4
    Very easy to use
  • 3
    It's made development super fast
  • 3
    Great
  • 3
    Brilliant for startups
  • 2
    The concurrent updates create a great experience
  • 2
    Cloud functions
  • 2
    Free hosting
  • 2
    Push notification
  • 2
    Free authentication solution
  • 2
    JS Offline and Sync suport
  • 2
    Low battery consumption
  • 2
    I can quickly create static web apps with no backend
  • 2
    Great all-round functionality
  • 1
    Large
  • 1
    Easy to use
  • 1
    Free SSL
  • 1
    CDN & cache out of the box
  • 1
    Faster workflow
  • 1
    .net
  • 1
    Easy Reactjs integration
  • 1
    Google's support
  • 1
    Good Free Limits
  • 1
    Serverless
CONS OF FIREBASE
  • 31
    Can become expensive
  • 15
    No open source, you depend on external company
  • 15
    Scalability is not infinite
  • 9
    Not Flexible Enough
  • 6
    Cant filter queries
  • 3
    Very unstable server
  • 3
    No Relational Data
  • 2
    No offline sync
  • 2
    Too many errors

related Firebase posts

Stephen Gheysens
Senior Solutions Engineer at Twilio · | 14 upvotes · 689.5K views

Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

See more
Tassanai Singprom

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools

Slack

See more
Socket.IO logo

Socket.IO

10.4K
8.9K
776
Realtime application framework (Node.JS server)
10.4K
8.9K
+ 1
776
PROS OF SOCKET.IO
  • 214
    Real-time
  • 141
    Event-based communication
  • 141
    Node.js
  • 102
    WebSockets
  • 101
    Open source
  • 26
    Binary streaming
  • 21
    No internet dependency
  • 10
    Large community
  • 9
    Fallback to polling if WebSockets not supported
  • 6
    Push notification
  • 5
    Ease of access and setup
CONS OF SOCKET.IO
  • 11
    Bad documentation
  • 4
    Githubs that complement it are mostly deprecated
  • 3
    Doesn't work on React Native
  • 2
    Websocket Errors
  • 2
    Small community

related Socket.IO posts

across_the_grid
Full-stack web developer · | 10 upvotes · 359.8K views
Shared insights
on
Socket.IOSocket.IONode.jsNode.jsExpressJSExpressJS

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

We are starting to work on a web-based platform aiming to connect artists (clients) and professional freelancers (service providers). In-app, timeline-based, real-time communication between users (& storing it), file transfers, and push notifications are essential core features. We are considering using Node.js, ExpressJS, React, MongoDB stack with Socket.IO & Apollo, or maybe using Real-Time Database and functionalities of Firebase.

See more
Pusher logo

Pusher

536
1.3K
234
Hosted APIs to build realtime apps with less code
536
1.3K
+ 1
234
PROS OF PUSHER
  • 55
    An easy way to give customers realtime features
  • 40
    Websockets
  • 35
    Simple
  • 27
    Easy to get started with
  • 25
    Free plan
  • 12
    Heroku Add-on
  • 11
    Easy and fast to configure and to understand
  • 9
    JSON
  • 6
    Azure Add-on
  • 5
    Support
  • 5
    Happy
  • 4
    Push notification
CONS OF PUSHER
  • 9
    Costly

related Pusher posts

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

See more
Kirill Shirinkin
Cloud and DevOps Consultant at mkdev · | 3 upvotes · 278.4K views
Shared insights
on
MattermostMattermostPusherPusherTwilioTwilio
at

Recently we finished long research on chat tool for our students and mentors. In the end we picked Mattermost Team Edition as the cheapest and most feature complete option. We did consider building everything from scratch and use something like Pusher or Twilio on a backend, but then we would have to implement all the desktop and mobile clients and all the features oursevles. Mattermost gave us flexible API, lots of built in or easy to install integrations and future-proof feature set. We are still integrating it with our main platform but so far the team, existing mentors and students are very happy.

See more
SignalR logo

SignalR

406
1.1K
122
A new library for ASP.NET developers that makes developing real-time web functionality easy.
406
1.1K
+ 1
122
PROS OF SIGNALR
  • 28
    Supports .NET server
  • 19
    Real-time
  • 15
    Free
  • 14
    Fallback to SSE, forever frame, long polling
  • 13
    WebSockets
  • 8
    JSON
  • 8
    Simple
  • 7
    Open source
  • 5
    Ease of use
  • 5
    Cool
  • 0
    Azure
CONS OF SIGNALR
  • 2
    Requires jQuery
  • 2
    Expertise hard to get
  • 1
    Weak iOS and Android support
  • 1
    Big differences between ASP.NET and Core versions

related SignalR posts

Shared insights
on
gRPCgRPCSignalRSignalR.NET.NET

We need to interact from several different Web applications (remote) to a client-side application (.exe in .NET Framework, Windows.Console under our controlled environment). From the web applications, we need to send and receive data and invoke methods to client-side .exe on javascript events like users onclick. SignalR is one of the .Net alternatives to do that, but it adds overhead for what we need. Is it better to add SignalR at both client-side application and remote web application, or use gRPC as it sounds lightest and is multilingual?

SignalR or gRPC are always sending and receiving data on the client-side (from browser to .exe and back to browser). And web application is used for graphical visualization of data to the user. There is no need for local .exe to send or interact with remote web API. Which architecture or framework do you suggest to use in this case?

See more
NATS logo

NATS

265
413
53
Lightweight publish-subscribe & distributed queueing messaging system
265
413
+ 1
53
PROS OF NATS
  • 21
    Fastest pub-sub system out there
  • 15
    Rock solid
  • 10
    Easy to grasp
  • 3
    Light-weight
  • 3
    Easy, Fast, Secure
  • 1
    Robust Security Model
CONS OF NATS
  • 1
    No Order
  • 1
    Persistence with Jetstream supported
  • 1
    No Persistence

related NATS posts

Reza Saadat
IoT Solutions Architect at GreenEdge · | 5 upvotes · 24.8K views
Shared insights
on
MQTTMQTTNATSNATS

I want to use NATS for my IoT Platform and replace it instead of the MQTT broker. is there any preferred added value to do that?

See more
PubNub logo

PubNub

178
429
238
Build real-time apps quickly and scale them globally.
178
429
+ 1
238
PROS OF PUBNUB
  • 36
    Massively scalable & easy to use
  • 25
    Easy setup
  • 20
    Reliable
  • 19
    Great support
  • 14
    Flexible to integrate to custom applications
  • 13
    High-Performance
  • 13
    Sockets at Scale
  • 13
    99.999% availability guarantees
  • 12
    High-Reliability
  • 12
    Multiplexing
  • 7
    Scalability
  • 5
    70+ SDKs
  • 5
    High-Availability
  • 4
    Security
  • 4
    Azure Add-on
  • 3
    Heroku Add-on
  • 3
    Easy to setup
  • 3
    Flexible
  • 3
    Presence
  • 2
    Analytics
  • 2
    Free Plan
  • 2
    Server-Side Cache
  • 2
    PhoneGap Plugin
  • 2
    AngularJS Adapter
  • 2
    Data Sync
  • 2
    Data Streams
  • 2
    Support
  • 1
    Easy setup and very reliable
  • 1
    High cost, going up more in Summer '15
  • 1
    Cool
  • 1
    Angular 2+ integration
  • 1
    Documentation, easy to use, great people/service
  • 1
    CTO stephen also is A++++++
  • 1
    Real time and easy to use.
  • 1
    Easy integration with iOS apps
CONS OF PUBNUB
  • 1
    Costly

related PubNub posts

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

See more
Shared insights
on
PubNubPubNubSocket.IOSocket.IO

I am trying to replace Socket.IO with PubNub. Provide the way to do it.

See more