Node.js · Theory

Buffer.alloc in Node.js

Theory

287/723

Don’t start Buffer.alloc (in node js) with jargon. Start with read a big CSV. That is the whole point.

Keep Buffer.alloc (in node js) small. Rohit should finish read a big CSV in a few lines, not a 40-line dump.

Buffer.alloc (in node js) exists so Rohit can keep read a big CSV correct in an upload job.

Rohit ships Buffer.alloc (in node js) in an upload job. That is the use case worth saying.

Buffer.alloc (in node js) miss — loading the whole file into RAM. Fix it before you talk about advanced Node.js.

After Buffer.alloc (in node js), Rohit should still remember loading the whole file into RAM.

Viva for Buffer.alloc (in node js) — what it is → createReadStream → the mistake (loading the whole file into RAM).

Exam tip

Say Buffer.alloc (in node js) in one breath, then createReadStream, then loading the whole file into RAM.

const buf = Buffer.from("PrepPilot", "utf8");
console.log(buf.toString("utf8"));
console.log(buf.length);

Buffer.alloc in Node.js — buffer holds raw binary data outside the V8 string heap.

DefBuffer.alloc (in node js) — Rohit uses it for read a big CSV in an upload job.
RuleBuffer.alloc (in node js) → createReadStream.
RememberBuffer.alloc (in node js) + an Express route (an upload job).
UseBuffer.alloc (in node js) in an upload job (read a big CSV).
TrapBuffer.alloc (in node js) — loading the whole file into RAM.
ExBuffer.alloc (in node js) → read a big CSV.