Alternatives to Liveblocks logo

Alternatives to Liveblocks

Firebase, Socket.IO, ws, Pusher, and Google Cloud Pub/Sub are the most popular alternatives and competitors to Liveblocks.
0
2
+ 1
0

What is Liveblocks and what are its top alternatives?

It is a fully hosted solution and complete toolkit to modularly embed collaborative experiences into your product remarkably fast.
Liveblocks is a tool in the Realtime Backend / API category of a tech stack.

Top Alternatives to Liveblocks

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

  • ws
    ws

    It is a simple to use, blazing fast, and thoroughly tested WebSocket client and server implementation. ...

  • Pusher
    Pusher

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

  • Google Cloud Pub/Sub
    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

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

  • Supabase
    Supabase

    Supabase is currently in early-Alpha .It is an open-source Firebase alternative. It adds realtime and RESTful APIs to your PostgreSQL database without a single line of code. ...

Liveblocks alternatives & related posts

Firebase logo

Firebase

39.9K
34.3K
2K
The Realtime App Platform
39.9K
34.3K
+ 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
    Super fast development
  • 8
    Angularfire is an amazing addition!
  • 8
    Chat
  • 6
    Built in user auth/oauth
  • 6
    Ios adaptor
  • 6
    Awesome next-gen backend
  • 6
    Firebase hosting
  • 4
    Speed of light
  • 4
    Very easy to use
  • 3
    Great
  • 3
    It's made development super fast
  • 3
    Brilliant for startups
  • 2
    The concurrent updates create a great experience
  • 2
    Push notification
  • 2
    .net
  • 2
    Cloud functions
  • 2
    Free hosting
  • 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
    Faster workflow
  • 1
    Google's support
  • 1
    CDN & cache out of the box
  • 1
    Easy Reactjs integration
  • 1
    Simple and easy
  • 1
    Good Free Limits
  • 1
    Serverless
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
Socket.IO logo

Socket.IO

12.9K
10.6K
784
Realtime application framework (Node.JS server)
12.9K
10.6K
+ 1
784
PROS OF SOCKET.IO
  • 219
    Real-time
  • 142
    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 · 419.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
ws logo

ws

845
188
0
A Node.js WebSocket library
845
188
+ 1
0
PROS OF WS
    Be the first to leave a pro
    CONS OF WS
      Be the first to leave a con

      related ws posts

      Pusher logo

      Pusher

      602
      1.4K
      234
      Hosted APIs to build realtime apps with less code
      602
      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 · 469.9K 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
      Google Cloud Pub/Sub logo

      Google Cloud Pub/Sub

      512
      421
      13
      Global service for real-time and reliable messaging and streaming data
      512
      421
      + 1
      13
      PROS OF GOOGLE CLOUD PUB/SUB
      • 9
        Easy to set-up and start with
      • 2
        A great choice for microservice architecture
      • 2
        Efficient and practical for complex systems
      CONS OF GOOGLE CLOUD PUB/SUB
      • 2
        Need integration with stackdriver for monitoring

      related Google Cloud Pub/Sub posts

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

      See more
      SignalR logo

      SignalR

      485
      1.2K
      146
      A new library for ASP.NET developers that makes developing real-time web functionality easy.
      485
      1.2K
      + 1
      146
      PROS OF SIGNALR
      • 32
        Supports .NET server
      • 25
        Real-time
      • 18
        Free
      • 16
        Fallback to SSE, forever frame, long polling
      • 15
        WebSockets
      • 10
        Simple
      • 9
        Open source
      • 8
        Ease of use
      • 8
        JSON
      • 5
        Cool
      • 0
        Azure
      CONS OF SIGNALR
      • 2
        Expertise hard to get
      • 2
        Requires jQuery
      • 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

      362
      480
      60
      Lightweight publish-subscribe & distributed queueing messaging system
      362
      480
      + 1
      60
      PROS OF NATS
      • 22
        Fastest pub-sub system out there
      • 16
        Rock solid
      • 12
        Easy to grasp
      • 4
        Light-weight
      • 4
        Easy, Fast, Secure
      • 2
        Robust Security Model
      CONS OF NATS
      • 2
        Persistence with Jetstream supported
      • 1
        No Order
      • 1
        No Persistence

      related NATS posts

      Reza Saadat
      IoT Solutions Architect at GreenEdge · | 5 upvotes · 84.4K 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
      Supabase logo

      Supabase

      314
      325
      24
      The open source Firebase alternative
      314
      325
      + 1
      24
      PROS OF SUPABASE
      • 6
        Relational Database
      • 5
        Self hosting
      • 3
        Free
      • 2
        Open source
      • 2
        Postgres hosting
      • 2
        Easy deployment
      • 1
        Focus on product, not on deployment
      • 1
        Faster development
      • 1
        Realtime
      • 1
        Huge time-saver
      CONS OF SUPABASE
      • 0
        No cons

      related Supabase posts

      Hello,

      I'm in the midst of reviewing an old CRUD SAAS I have running on Angular 7 with a MariaDB backend and Laravel PHP. Presently is hosted on a couple of Linode servers- and really feeling the weight, especially with the looming need to upgrade to A15 and meet the pace and scalability occurring (for context, the SAAS turns in over 24k USD monthly in subscriptions- so I have concerns around the impact of a new stack on existing clients). Additionally, I manage a Kotlin and Swift codebase for appdev.

      I'm looking at moving towards Flutter for a singular codebase, and something serverless but still relational- like Supabase. In the past, I ran my own Auth services- but it was a ton of work to setup and maintain, so looking at using Firebase for Auth services (I know Supabase has Auth as well, but I wonder if it's as reliable and frequently maintained as Firebase?) Supabase has a FlutterSDK as well which makes things much simpler. Planning on maintaining microservices like Stripe etc for functional aspects.

      I would love some insight from those who have done a tech stack transition, what should I be aware of- those who have produced in Flutter or a similar stack, what am I walking into without knowing?

      See more