Node arrived on the scene around the time the WebSocket protocol was drafted. Node’s fast, evented approach to server-side programming was a perfect pairing for WebSocket. Out of that marriage emerged the popular socket.io framework: an instant favorite used heavily in the first Node Knockout competition.
The WebSocket module ecosystem
WebSocket modules can be divided up into three categories. The first are protocol implementations (drivers) which focus on high performance of and standards compliance to the WebSocket protocol. Like the http module, they provide a low-level implementation.
WebSocket emulators build on the protocol implementations by adding fallback WebSocket-like functionality using transports like XHR long-polling or htmlfile. These modules exist as a compatibility layer to enable real-time for browsers or networks that do support WebSocket.
Lastly, there are high-level modules which build on the emulation layer with conveniences such as broadcast messages, channels, rooms, and custom event emitters.
The intention of this article is not to provide an exhaustive list of all modules existing in Node space as there are simply too many to cover. However, if there is one I missed that will add to the discussion, please make a comment!
The WebSocket Protocol implementations
Drivers implement the core WebSocket functionality by providing both server and client interfaces. Typically, they are not used directly. However, if you know your environment has reliable WebSocket support (as there is no falling back), drivers provide a nice minimal surface to build on.
Here are some popular drivers:
The ws module backs the popular socket.io framework. It boasts the fastest compliant implementation of WebSocket and includes a helpful wscat command line tool for debugging WebSocket servers. It requires compilation of native add-ons.
The websocket module is another popular implementation that has existed for a while. It is fast and can be run without native module compilation (although not as efficiently).
The WebSocket Emulation modules
Unfortunately, WebSocket does not work everywhere. Even browsers supporting WebSocket run into issues if the network isn’t conducive to WebSocket. Here is where emulation modules come into play. They employ different strategies to ensure the browser gets the best possible real-time transport available (which ultimately is WebSocket).
Here are some popular emulation modules:
The sockjs module is built on faye-websocket and is a mature WebSocket emulation layer that follows a downgrade path. This means it will try the best protocol first and then fallback, if necessary, until it finds a working transport. It is used in conjunction with the client-side sockjs-client module. It includes a number of faster streaming transports as well as polling. Implementations exist for a number of other, non-Node, platforms if interoperability is important.
The engine.io module is newer on the scene. It is built on ws by the guys behind socket.io. It follows an upgrade path. This means it will try the most reliable protocol first and then upgrade to the best available protocol. The reasons stem from failures in the downgrade path detailed in the readme. It is used in conjunction with the client-side engine-io-client module.
High-level API Sugar
If you need a high-functioning real-time engine without a ton of bells and whistles, sockjs or engine.io is the way to go. However, if your applications needs channels, rooms, broadcasting, or custom event emitters, there are options for that as well.
Since numerous modules fall under this category, we will only cover a few here:
The socket.io module is the original wildly popular real-time engine. It includes features such as broadcasting, rooms, namespaces, and custom event emitters. It is “still” in development, but version 1.0 integrates with engine.io (the latest stable 0.9.x does not).
Modules: websocket-multiplex and shoe
The primus module wraps around several real-time frameworks, such as engine.io and sockjs, to prevent vender lock-in. It includes a number of modules that add the functionality you need: channels (multiplexing), custom event emitters, rooms, etc.
A fireside chat about real-time engines
Here’s a little advice from one who has “walked through the fire” of debugging real-time engines:
- Use only what you need and nothing more. In my experience, staying at the emulation layer with a library like sockjs or engine.io and building only what I need has proven easier to debug. I haven’t used primus personally, but I like the modular approach there. However, something feature-rich like socket.io enables faster prototyping of ideas.
- The downgrade approach is slightly faster to set up, but has problems on some networks; upgrade approach is slightly slower, but more reliable. Both approaches have their merits. I’m curious as to how that is playing out for others.
- WebSocket running on port 80 can be the most troublesome for corporate firewalls as everybody likes to have their hands on that port! Try switching to 443 (SSL) or any other port to fix problems upgrading the protocol.
Keeping it real-time
In this article, we surveyed a number of WebSocket modules in Node. We started with implementations (drivers) which provide the core WebSocket protocol. Then we looked at emulation modules which wrap WebSocket and a number of fallback transports in a common API. Lastly, we looked at high-level sugar modules that extend the emulation layers with additional conveniences.
WebSocket has become a game-changer in web development by enabling games, frameworks, and applications that were not possible before. What will you build?