Is it worth separating sockets from a monolith and what server characteristics should I look at?

Question

Software design

There is a monolith built on React + Laravel. We decided that we need to switch to a microservice architecture, take 2 servers for the front + back, 1 server for the database and 1 server for load balancing.
There was a question what to do with sockets? Online is now about 5-6k, but it is growing. For the future, after reading, I realized that it seems to be how it is necessary to take out the sockets separately. If you take it out, what characteristics of the server should you pay attention to at all? For bandwidth, RAM or what? Thank you.

Answer 1

Costs. What characteristics to take should be decided based on the load and resource consumption of your solution. We don't know what your sockets are on. Maybe it's socket.io, or maybe centrifugo, or maybe you even raised them in PHP