Websocket for a page or for the entire site?

Question

Node.js

Hello. I decided to learn Node.js and rewrite my online store from php to node.js + express.js. Along the way, there is an idea to implement a real-time basket. The essence of such a basket is that it is a kind of "room" for the manager and the client. Client access is provided via the link. It is necessary that the client sees all the changes in this virtual basket without reloading the page. The manager throws the goods for the client, and at the end he can place an order by clicking the button to place an order.

But the essence of the matter is different. Since the site has a flow of customers and it is increasing. Will websocket + site take out together? If not, all of a sudden, is it possible to somehow raise a web socket for one page, and the rest would work without a bunch.

I hope it's not hard to explain. Thank you for your attention

Answer 1

Do you have RPS metrics and overall metrics? Without them, it's stupid to give recommendations, but in 99% socket.io will take out your "highload". Moreover, socket processing is not entirely related to the tasks of the site, they have a different context.
Summarizing, I can say for sure that the load will not be as significant as you think. Unless you store socket subscription data not in LRU (memory), but immediately use redis, memcache, etc.