A journey with ws, Socket.IO, Engine.IO, and Primus
For a current project at WhoScored, I needed to learn JavaScript, Node.JS and WebSocket channel, after seven years of writing web applications with Java and Spring framework. We wanted an application that can send data to thousands of concurrent users, and Node.JS appeared to be the right way of doing it with its event-driven, non-blocking I/O model that can scale up easily.
Compared Frameworks
* einaros / ws
* Socket.IO
* Engine.IO
* Primus
Performance limits
* Changing the flow based on limitations
* Test 1: The impact of data size
* Test 2: The impact of concurrent connection size
* Test 3: The impact of data broadcasting frequency
Your new post is loading...