node.js - Bottleneck with sockets approach? -
The idea of creating a real-time app where users can collaborate to solve this type of problem is a node. Js + socket.io found
I hear from other developers that my server will give users an obstacle to the number of sockets. If I have hundreds of users who support at the same time, then the number of open sockets is over And the users will not be able to connect. Is this a legitimate concern?
Update: Also like the note I'm looking to use SockJS instead of Socket.io is one of these libraries besides For hundreds of users I do not think this is a matter of concern. As you think there is a consistent connection between the socket client and the server and both parties can start sending data at any time. Keeping them open, there is no problem in handling the load in the context of the sender / second. Socket.io can easily handle up to 1000 concurrent connections. But it will fail if he is sending more than 8-10k messages per second. You will hit the load barrier before your chairs end. In most cases handling more concurrent users, the translation of high load is translated. Then do not worry about lowering the sockets
Comments
Post a Comment