Pusher VS Socket.io

Pusher Channels is a real-time notifications service that empowers developers to swiftly integrate real-time functionality, like live notifications and chat, into web and mobile apps using WebSockets. Pusher is known for reliability and scalability and is used by Buffer, GitHub, and Datadog.

Pusher

Typically, you don't do websockets. There are some great products out there that give you the same capabilities. I recently started working with Pusher for my Remix applications and am loving it!

According to Vercel's website SocketIO is NOT supported, however Pusher Channels is recommended in it's place. Not sure what it is, but it supposedly is supported by vercel and potentially can help.

Pusher is a hosted service that makes it super-easy to add real-time data and functionality to web and mobile applications. It sits as a real-time layer between your servers and your clients. Pusher maintains persistent connections to the clients — over WebSocket if possible and falling back to HTTP-based connectivity — so that as soon as your servers have new data that they want to push to the clients they can do, instantly via Pusher.

Then watchPosition from @react-native-community/geolocation is definitely the way to go. Here's a link to the example in their repo. This will constantly update the position state variable, which you can then send to a realtime service which other users are subscribed to and consuming. (Depending on your implementation, could be a websocket or some pub/sub service... I've worked with Pusher Channels before for something similar.)

An easy way to start with is to use external Pusher channels service It requires 0 devops and everything works very well, for free at least at the beginning. However, like any external service, it can't scale without paying. "Pay as you grow".

I see that NextJS now recommends a pub/sub approach Vercel Support Your client will need to subscribe to the events from a 3rd party service like Pusher Channels and the Pub should be handled by a serverless function

Centrifugo is very similar to pusher.com Channels product (https://pusher.com/channels) – but self-hosted. Also – somewhat similar to socket.io - but not a library, so can work with any backend. Centrifugo is pretty unique in terms of available features sum – so can't say that there is a direct analogue I've heard about - sth from one product, sth from another, sth unique. And of course there are alternatives which can do what Centrifugo can't since the market of real-time servers is quite big.

Complexity: WebSockets require you to handle connection lifecycle events, such as errors and reconnections. While the code example I provided could suffice for simple use cases, more complex use cases might arise, like automatic reconnection and queueing messages sent by the client when the connection wasn't open. For that, you can either extend this code or use an external library like react-use-websocket for a relatively lightweight react implementation or socketio for both client and server SDKs.

Socket.IO

aiortc can be easily integrated with other python libraries such as aiohttp for web server as well as other third party libraries such as socket.io for real time event handling

We need to allow users to get real-time updates when a new video, comment, or like is created or when a video is updated. To do this, we'll use Socket.IO. We'll write a custom Socket implementation in our Strapi project to handle real-time functionalities.

uWebSockets is web server written in C++. In our case we'll be using uWebSockets.js which has bindings to NodeJS. It can be used as a usual web server but the main feature is its WebSocket server. It is 10x faster than Socket.IO and 8.5x faster than Fastify. I have to say I haven't benchmarked it myself. I decided to use uWebSockets just because it feels more pure to my taste. For example it doesn't require Express it runs on it's own, also it doesn't have any additional wrappers or helper functions that "babysit" you. You just get a message and you handle it whatever the way you want it. So if you're ok with that approach and you need a faster WebSocket server then you should use uWebSockets.

This tutorial will guide you through building a real-time notification system for a chat app using React and Socket.io. React is ideal for creating dynamic, reusable components and efficiently managing your app’s state. Socket.io enables real-time, bidirectional communication between the server and the browser, allowing instant message delivery without page reloads. This combination lets you build a responsive, interactive UI that communicates with the server in real-time.

1. Real-Time Notifications with Socket.io

5. Socket.io

Socket.io: Real-time communication used by the application to provide live update of some feature and settings.

Websockets in Node.js There are various libraries that let you create a ws server:- https://www.npmjs.com/package/websocket https://github.com/websockets/ws https://socket.io/