Alternatives to PubNub logo

Alternatives to PubNub

Pusher, Socket.IO, SendBird, Stream, and Kafka are the most popular alternatives and competitors to PubNub.
236
457
+ 1
238

What is PubNub and what are its top alternatives?

PubNub is a real-time Data Stream Network (DSN) that provides scalable messaging for web, mobile, and IoT applications. Its key features include low-latency communication, push notifications, presence detection, stream analytics, and messaging history. However, PubNub can be expensive for high usage scenarios, has limited message size, and lacks full control over data residency and compliance.

  1. Firebase: Firebase, owned by Google, offers real-time database, authentication, and hosting services. It provides real-time synchronization, offline support, and robust security features. Pros include integration with Google services and Firebase's easy-to-use interfaces. However, Firebase may have limitations in scalability for very large applications.

  2. Pusher: Pusher is a hosted service that enables developers to add real-time functionalities to their applications. It offers channels, events, and presence features for real-time communication. Pros include easy setup and comprehensive documentation. However, Pusher may be cost-prohibitive for high message volume.

  3. Socket.io: Socket.io is a JavaScript library for real-time web applications. It enables bidirectional communication between clients and servers through websockets. Key features include event-driven architecture and room support. Pros of Socket.io include its adaptability and ease of use. However, it may not be as scalable as other solutions.

  4. AWS IoT Core: Amazon Web Services (AWS) IoT Core is a managed cloud platform that enables devices to connect with cloud applications reliably and securely. It offers device management, data processing, and rules engine. Pros include integration with other AWS services and robust security features. However, AWS IoT Core may have a steeper learning curve.

  5. SignalR: SignalR is a library for ASP.NET developers to add real-time web functionality to their applications. It supports WebSockets, Server-Sent Events, and long polling. Pros include seamless integration with ASP.NET and ease of scaling. However, SignalR may be limited in features compared to other solutions.

  6. Meteor: Meteor is a full-stack platform for developing web and mobile applications in pure JavaScript. It includes real-time updates, data synchronization, and hot code push. Pros of Meteor include rapid prototyping and cross-platform development. However, Meteor may have performance issues with very large applications.

  7. RabbitMQ: RabbitMQ is an open-source message broker software that implements the Advanced Message Queuing Protocol (AMQP). It allows for reliable messaging between systems and applications. Pros include flexibility in routing messages and high availability. However, RabbitMQ may require more configuration and maintenance.

  8. Kafka: Apache Kafka is an open-source distributed event streaming platform used for building real-time data pipelines and streaming applications. It provides fault tolerance, high throughput, and scalability. Pros include horizontal scalability and durability of messages. However, Kafka may have a steeper learning curve.

  9. Ably: Ably is a real-time data delivery platform that offers Pub/Sub messaging, presence detection, and message history. It provides global edge messaging, guaranteed message delivery, and reactive programming libraries. Pros include low-latency messaging and robust infrastructure. However, Ably may have limited integrations compared to other solutions.

  10. NATS: NATS is a lightweight and high-performance messaging system for cloud native applications. It offers publish-subscribe messaging, request-reply messaging, and scaling capabilities. Pros include simplicity of design and high performance. However, NATS may lack some advanced features present in other solutions.

Top Alternatives to PubNub

  • Pusher
    Pusher

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

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

  • SendBird
    SendBird

    SendBird is a Messaging SDK, Chat API, and fully managed chat infrastructure for your mobile apps and websites. Embeddable chat for iOS, Android, JavaScript, Unity, .NET. ...

  • Stream
    Stream

    Stream allows you to build scalable feeds, activity streams, and chat. Stream’s simple, yet powerful API’s and SDKs are used by some of the largest and most popular applications for feeds and chat. SDKs available for most popular languages. ...

  • Kafka
    Kafka

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

  • Ably
    Ably

    Ably offers WebSockets, stream resume, history, presence, and managed third-party integrations to make it simple to build, extend, and deliver digital realtime experiences at scale. ...

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

  • Twilio
    Twilio

    Twilio offers developers a powerful API for phone services to make and receive phone calls, and send and receive text messages. Their product allows programmers to more easily integrate various communication methods into their software and programs. ...

PubNub alternatives & related posts

Pusher logo

Pusher

601
1.4K
234
Hosted APIs to build realtime apps with less code
601
1.4K
+ 1
234
PROS OF PUSHER
  • 55
    An easy way to give customers realtime features
  • 40
    Websockets
  • 34
    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
    Happy
  • 6
    Azure Add-on
  • 5
    Support
  • 4
    Push notification
CONS OF PUSHER
  • 10
    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 · 471.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
Socket.IO logo

Socket.IO

13K
10.7K
785
Realtime application framework (Node.JS server)
13K
10.7K
+ 1
785
PROS OF SOCKET.IO
  • 219
    Real-time
  • 143
    Node.js
  • 141
    Event-based communication
  • 102
    Open source
  • 102
    WebSockets
  • 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
  • 1
    Test
CONS OF SOCKET.IO
  • 12
    Bad documentation
  • 4
    Githubs that complement it are mostly deprecated
  • 3
    Doesn't work on React Native
  • 2
    Small community
  • 2
    Websocket Errors

related Socket.IO posts

across_the_grid
Full-stack web developer · | 10 upvotes · 421.2K 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
SendBird logo

SendBird

138
402
78
A Complete Chat Platform, Messaging and Chat SDK and API
138
402
+ 1
78
PROS OF SENDBIRD
  • 13
    Active support is impressive. (Support for private deve
  • 10
    Pre-built UI for major platforms
  • 10
    Easy to use
  • 8
    Migration API for customers using other chat services
  • 7
    Scalability is awesome
  • 7
    First chat SDK officially supports Xamarin
  • 5
    Because my product guy told me to
  • 5
    Unlimited number of users in public chat
  • 5
    Cool product
  • 4
    Flexible message format ex) json, xml
  • 2
    Out of the box api and features
  • 2
    Intuitive and feature-packed
CONS OF SENDBIRD
  • 2
    Policy on concurrent users leads to overages and overch
  • 2
    Prices ramp up exponentially

related SendBird posts

Shared insights
on
StreamStreamSendBirdSendBirdFlutterFlutter

I am interested in using a chat SDK for a community mobile Flutter app. I am between SendBird and Stream. I currently have 2,000 monthly active users and plan to have close to 5,000 active users chatting on the app. Has anyone used either and had good/bad experiences? Currently, there is no chat functionality, and we would like to have a 1-to-1 user chat, group chat, and large community chat capabilities.

See more
Yeongju Park
SW Web Engineer at Sense Korea · | 4 upvotes · 74.6K views
Shared insights
on
MSSQLMSSQLSendBirdSendBirdCometChatCometChat

I am considering which chat solution to choose between CometChat and SendBird, for our new app. The condition is, the app is going to run in a private network and has to connect with MSSQL. Any advice on other things I have to consider before choosing one, or is there another chat service you would recommend? Thank you!

See more
Stream logo

Stream

216
223
54
Build scalable feeds, activity streams & chat in a few hours instead of months.
216
223
+ 1
54
PROS OF STREAM
  • 18
    Up and running in few minutes
  • 18
    Integrates via easy-to-use REST API
  • 18
    It's easy to setup with the minimum coding
CONS OF STREAM
    Be the first to leave a con

    related Stream posts

    Kafka logo

    Kafka

    23K
    21.6K
    607
    Distributed, fault tolerant, high throughput pub-sub messaging system
    23K
    21.6K
    + 1
    607
    PROS OF KAFKA
    • 126
      High-throughput
    • 119
      Distributed
    • 92
      Scalable
    • 86
      High-Performance
    • 66
      Durable
    • 38
      Publish-Subscribe
    • 19
      Simple-to-use
    • 18
      Open source
    • 12
      Written in Scala and java. Runs on JVM
    • 9
      Message broker + Streaming system
    • 4
      KSQL
    • 4
      Avro schema integration
    • 4
      Robust
    • 3
      Suport Multiple clients
    • 2
      Extremely good parallelism constructs
    • 2
      Partioned, replayable log
    • 1
      Simple publisher / multi-subscriber model
    • 1
      Fun
    • 1
      Flexible
    CONS OF KAFKA
    • 32
      Non-Java clients are second-class citizens
    • 29
      Needs Zookeeper
    • 9
      Operational difficulties
    • 5
      Terrible Packaging

    related Kafka posts

    Eric Colson
    Chief Algorithms Officer at Stitch Fix · | 21 upvotes · 6.1M 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
    Ably logo

    Ably

    55
    95
    74
    The platform to power synchronized digital experiences in realtime, at scale.
    55
    95
    + 1
    74
    PROS OF ABLY
    • 8
      WebSockets
    • 7
      Highly reliable
    • 6
      SSE
    • 6
      Massive scalability
    • 6
      Great technical support
    • 5
      Channel Presence
    • 5
      Free plan
    • 5
      Channel History
    • 5
      Message queueing
    • 5
      Global cloud network of data centers
    • 4
      WebHooks
    • 4
      MQTT
    • 4
      Consistently high performance
    • 4
      Third-party cloud integrations
    CONS OF ABLY
      Be the first to leave a con

      related Ably posts

      Firebase logo

      Firebase

      40.1K
      34.4K
      2K
      The Realtime App Platform
      40.1K
      34.4K
      + 1
      2K
      PROS OF FIREBASE
      • 371
        Realtime backend made easy
      • 270
        Fast and responsive
      • 242
        Easy setup
      • 215
        Real-time
      • 191
        JSON
      • 134
        Free
      • 128
        Backed by google
      • 83
        Angular adaptor
      • 68
        Reliable
      • 36
        Great customer support
      • 32
        Great documentation
      • 25
        Real-time synchronization
      • 21
        Mobile friendly
      • 18
        Rapid prototyping
      • 14
        Great security
      • 12
        Automatic scaling
      • 11
        Freakingly awesome
      • 8
        Chat
      • 8
        Angularfire is an amazing addition!
      • 8
        Super fast development
      • 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
        Great
      • 3
        It's made development super fast
      • 3
        Brilliant for startups
      • 2
        Free hosting
      • 2
        Cloud functions
      • 2
        JS Offline and Sync suport
      • 2
        Low battery consumption
      • 2
        .net
      • 2
        The concurrent updates create a great experience
      • 2
        Push notification
      • 2
        I can quickly create static web apps with no backend
      • 2
        Great all-round functionality
      • 2
        Free authentication solution
      • 1
        Easy Reactjs integration
      • 1
        Google's support
      • 1
        Free SSL
      • 1
        CDN & cache out of the box
      • 1
        Easy to use
      • 1
        Large
      • 1
        Faster workflow
      • 1
        Serverless
      • 1
        Good Free Limits
      • 1
        Simple and easy
      CONS OF FIREBASE
      • 31
        Can become expensive
      • 16
        No open source, you depend on external company
      • 15
        Scalability is not infinite
      • 9
        Not Flexible Enough
      • 7
        Cant filter queries
      • 3
        Very unstable server
      • 3
        No Relational Data
      • 2
        Too many errors
      • 2
        No offline sync

      related Firebase posts

      Stephen Gheysens
      Lead Solutions Engineer at Inscribe · | 14 upvotes · 1.8M 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
      Twilio logo

      Twilio

      11K
      8.5K
      521
      Bring voice and messaging to your web and mobile applications.
      11K
      8.5K
      + 1
      521
      PROS OF TWILIO
      • 148
        Powerful, simple, and well documented api
      • 88
        RESTful API
      • 66
        Clear pricing
      • 61
        Great sms services
      • 58
        Low cost of entry
      • 29
        Global SMS Gateway
      • 14
        Good value
      • 12
        Cloud IVR
      • 11
        Simple
      • 11
        Extremely simple to integrate with rails
      • 6
        Great for startups
      • 5
        SMS
      • 3
        Great developer program
      • 3
        Hassle free
      • 2
        Text me the app pages
      • 1
        New Features constantly rolling out
      • 1
        Many deployment options, from build from scratch to buy
      • 1
        Easy integration
      • 1
        Two factor authentication
      CONS OF TWILIO
      • 4
        Predictable pricing
      • 2
        Expensive

      related Twilio posts

      Ravi Sathanapalli
      Director Product Management at Centime · | 6 upvotes · 96K views
      Shared insights
      on
      TwilioTwilioAmazon SNSAmazon SNS

      Hi, We are looking to implement 2FA - so that users would be sent a Verification code over their Email and SMS to their phone.

      We faced some limitations with Amazon SNS where we could either send the verification code to email OR to the phone number, while we want to send it to both.

      We also are looking to make the 2FA more flexible by adding any other options later on.

      What are the best alternatives to SNS for this use case and purpose? Looked at Twilio but want to explore other options before making a decision.

      Would be great to know what the experience with Twilio has been, especially the limitations/issues with Twilio...

      Appreciate any input from users of Twilio and others who have had similar use cases.

      See more
      Cheri Booth
      Vendor Relationship Manager at Storage Asset Management · | 6 upvotes · 44.8K views
      Shared insights
      on
      ClickatellClickatellTwilioTwilio

      Searching for options for SMS that integrates with SiteLink and will allow personalization of text and tracking of both incoming/outgoing messages with reporting (Time, date, call#, etc) Have been looking at Twilio, and seems most leaning toward this. Are there any other options known that integrate into SiteLink? Also looked at Clickatell.

      See more