I have read many articles and watched many tutorial videos, but the common ground for most of the material is to Publish changes to ALL users. Not Subscribing and get information what concerns just the user who is logged in.
The other common ground is Websockets protocol. There seems to be many other ways to skin this cat (Mark Twain) and I have some doubt which one to chose.
What I am searching for is a way for the user to login and connect to a server (Websocket server?) and say something like “Hey, I am Joe, please keep me updated on MY stuff”.
I have managed to set up a websocket server, but I only gets more confused how to proceed. How to think? The closest I have found is this and found also this. But this is above my pay grade. I do understand nothing.
In this stage I am mostly interested in “how to think”? No language specific.
We’re talking about different levels here. Websockets is a network communication protocol at the same protocol level as HTTP, whereas NATS is a message-passing system that runs on top of network protocols like TCP or Websockets.
I am not familiar with Socket.io and cannot tell you anything that’s not already in their docs. It seems that Socket.io does have some sort of broadcast mechanism using so-called rooms that allow sending messages to clients who joined that room. This sounds quite like what you are looking for—a solution to publish messages to subscribed clients.