1
A 'view' in Node.js refers to creating a new buffer that shares the same memory as an existing buffer but with a different start and end offset.
2
It allows you to work with subsets of a larger buffer efficiently without copying the data.

Difficulty: 6/10

Topics: Memory Management, TypedArrays, Binary Protocols

0-2 years experience

1
Imagine you're reading a binary file containing 32-bit integers. If you read this into a Node.js Buffer, how would you use a TypedArray view to read those integers without copying the data?
2
Suppose you create a Uint8Array view over a Node.js Buffer, and then you change a value at index 0 in the view. What happens to the original Buffer? How would you copy the data instead if you wanted to prevent this?

2-5 years experience

1
We have a service parsing a custom binary protocol over TCP. We noticed that when we create an Int32Array view directly on the incoming buffer slice, it occasionally throws a 'RangeError: start offset of Int32Array must be a multiple of 4'. Why is this happening, and how would you fix it without copying the entire buffer?
2
A developer on your team is debugging a memory leak. They noticed that slicing a large 100MB buffer to get a tiny 10-byte header view keeps the entire 100MB in memory. Why does this happen, and how would you refactor this to allow the garbage collector to reclaim the unused 100MB?

5-8 years experience

1
We are building a high-throughput WebSockets server in Node.js that processes binary payloads. To maximize throughput, we want to implement zero-copy parsing of incoming frames. How would you design the buffer management layer using ArrayBuffer and multiple TypedArray views to parse headers and payloads concurrently without GC thrashing?
2
You're reviewing code for a media streaming service that parses mixed-endian binary metadata. The developer used standard TypedArrays, but it's failing on certain CPU architectures. How would you use DataView to resolve the endianness issues, and what are the performance tradeoffs of DataView versus TypedArrays in Node.js?

8+ years experience

1
We are designing a Node.js native addon (using N-API) that processes real-time video frames from a camera feed. We need to pass these frames to JS for rendering. How would you architect the memory sharing between the C++ layer and the V8 heap using SharedArrayBuffer or Buffer views to achieve zero-copy transfer, and what are the synchronization risks we need to mitigate?
2
Your organization is migrating a legacy, high-volume networking library from Node's legacy Buffer APIs to standard JS Uint8Array and ArrayBuffer to make it cross-platform (runnable in Cloudflare Workers and browsers). What architectural challenges do you foresee regarding buffer views, memory allocation, and API compatibility, and how would you structure the migration?

❓What is the difference between Buffer.alloc() and Buffer.allocUnsafe() when initializing memory for views?
❓How does Buffer.prototype.slice() differ from TypedArray.prototype.slice() in terms of memory allocation?
❓When would you choose DataView over a specific TypedArray like Float64Array?