Socket.io VS deepstream.io

You need something that allows two-way communication. You can build your own using web sockets or socket.io like the other user said, or use something with two-way support built in.

What do you use socket.io for? I mean, you can just use Supabase realtime features, right?

We need to add socket.io to our project:

Create a node app, and use npm to add express and socket.io. Express handles the regular API endpoints, socket io handles websockets.

The switch wasn't that bad. We migrated a smaller Vue 2 and used Element Plus for the UI. We ran into problems with Vite since it requires ES modules for all your libs. We ended up ditching moment, axios, and sockjs and replaced them with dayjs, VueUse useFetch() and socket.io to make Vite happy. What we did was manually copy over one component at a time and rewrote any mixins as composition API functions. The large app took me a month to rewrite and we used Quasar for that after popular demand from the dev team. We standardized around the script setup syntax since it is cleaner to follow than plain setup().

I would probably set up a separate socket.io server for the real-time functionality, but load all the chat data for each page like you normally would from the database in +page.server.js load functions. The websocket server would then handle all the real-time stuff in the client after the initial data is loaded. This would allow you to still take full advantage of SSR.

Socket.io is the best Node.js server and web framework for creating real-time web applications. It enables event-based communication between the Node.js server and the browser. Socket.IO acts as a backend library for Node.js and as a frontend library in the browser.

After reading a couple articles and watching some tutorial videos, we realised that dealing with WebRTC natively is quite cumbersome. Due to this, PeerJS came handy to abstract away some configurations around WebRTC. While implementing peer-to-peer communication, there must be a signalling server for the purpose of keeping in sync the state/-s (muted, camera is off and etc.) between peers. Therefore, SocketIO played a role of signalling server. Basic authentication layer was integrated via Auth0 to implement certain features.

As of socket.io version 4.4.0 there is now built in support for acknowledgement timeouts. We pass a timeout argument of 30000 milliseconds (30 seconds) which will throw an error if our server does not send back an acknowledgement within that time period. If the timeout it hit, the leaveRoom() function will disconnect the socket and redirect the user back to the login page where they can try to join again.

For socket.io handling i use package gosf-socketio, when recieving a call from client i get channel struct and only available thing to use is .Request() which returns http.Request type.

Deepstream is an open-source library for real-time web application development. The library, which is built with Node.js and Engine.io, helps developers build frontend web applications that perform real-time updates while requiring minimal backend code.

I'm working on a few projects, from one/two days to platforms.

The first is OS and is a simple nodeJS environment to deploy applications via lambda and express quickly. Sort of like nestJS except less decorators and more functional (https://vramework.io/). I already know of a few other colleagues that rolled their own propriety versions of this to support enterprise and cloud deployments so decided to OS it.

The other OS project is a strongly typed postgres/mysql driver. The idea is to generate typescript definitions directly from postgres (https://github.com/vramework/schemats) and then have a think layer ontop of pg-node that gives you strongly typed queries (https://github.com/vramework/postgres-typed).

An open-source project I spent a few years on the core team is https://deepstream.io/, a realtime-server that allows you to mix and match multiple streaming protocols (mqtt/websocket/others) and allow those clients to talk to each other using pub-sub and records. I'm not longer working for it but wanted to give it a shout out!

On a non OS project, I have been working on an immersive audio platform for a while now. The main goal is to allow users to pick and choose how audio books progress, and also have a live session mode which allows users to record their pulse / answer questions and a few other metrics and associate it with sentences. I pretty much built and deployed all of it but require some advice/brainstorming on how to proceed now. I built it to satisfy an itch when I was practicing shamanism during the first lockdown when I was in-between contracts / taking time off.

I also want to build a simple web-pages strategy game based around eco-education, but don't have the bandwidth . If anyone is interested in mixing together gamification and eco-village building might be a fun conversion to bounce ideas!

All the OS projects above were used to support my personal/a couple professional projects over the last few years.

Email in profile

https://deepstream.io is the closest and has a richer feature set (including a replicating document store), however it seems to have a small ecosystem / community / limited support options, and permissions do not seem as advanced.

https://nats.io is close but lower level. Has a large community and rich ecosystem however.

Then you can also mix and match lowever level technologies to achieve the particular set of tradeoffs you need. MQTT, AMQP as the protocol, mosquitto / rabbitmq/zeromq, then json-rpc on top ...

I can find socket.io, faye, deepstream.io , autobahn-js and nchan, centrifugo. Can you also explain why you chose it and if you had troubles with some other solution?