Residency guarantee for per-room sockets on distributed architectures

[nicholaswmin]

Assuming a 10 dyno/process formation, using ioredis and the adapters on socketio v4, ioredis v5.3

In the following example I'm instantiating something and assigning it to socket.data, like so:

io.use((socket, next) => {
  socket.data = new Cow()
 
  next()
});

io.on('connection', () => {
  socket.join(id_session)

  socket.data.moo() // moooo.
})    

Should I expect that this instance will survive for the duration of the connection or is there any chance of some serialising/deserialising taking place which is going to cause it to lose it's type and methods?

I'm only asking about the duration of the connection, i.e if the client disconnects the state is of course lost.

[darrachequesne]

Hi! Yes, the socket object is guaranteed to stay on the same Socket.IO server for the duration of the connection.

However, please note that if you enable Connection state recovery, then in that case the socket object will indeed be serialised upon disconnection and recreated upon reconnection if the recovery is successful.

[nicholaswmin]

Cheers Damien. In that case I'll assume that serialisation is possible and not guaranteed to maintain forwards compatibility just in case.