In this lesson, you will learn how to shrink your network footprint by stripping unnecessary framing metadata when streaming Protocol Buffers over WebSockets.
When sending Protobuf messages over WebSockets, the naive approach is to send one Protobuf message per WebSocket frame. However, every WebSocket frame includes its own header (at least 2–14 bytes). If you are sending high-frequency, small updates (like coordinate data or sensor readings), the overhead of these headers can quickly exceed the size of your actual payload, significantly degrading your throughput.
To optimize this, we implement Message Batching or Framing over a continuous stream. Instead of treating every Protobuf object as a distinct WebSocket frame, we concatenate multiple binary messages into a single buffer and send them together.
Implementing Message Delimitation
Since Protobuf is not self-delimiting, you must prefix each message with a "varint" that specifies the length of the following message. This allows the receiver to slice the binary stream correctly without relying on the WebSocket frame boundary.
// On the sender side:
const msg1 = myProto.encode(data1).finish();
const msg2 = myProto.encode(data2).finish();
// Prepend the length as a varint to each message
const frame1 = Buffer.concat([encodeVarint(msg1.length), msg1]);
const frame2 = Buffer.concat([encodeVarint(msg2.length), msg2]);
// Send one larger buffer to reduce WebSocket header overhead
socket.send(Buffer.concat([frame1, frame2]));
Why this works
By combining messages, you amortize the fixed cost of the WebSocket protocol overhead. Instead of 10 WebSocket headers for 10 small messages, you pay for one header, effectively increasing your application-level "goodput."
When the receiver gets the blob, it simply reads the length prefix, consumes that many bytes for the first message, and repeats the process until the buffer is exhausted. This pattern drastically reduces packet congestion and CPU context switching on both the Node.js server and the client.
Key Takeaway: By batching Protobuf messages with length-delimiting into single WebSocket frames, you slash network header overhead and maximize high-frequency data throughput.