Engineering notes
Articles for people who
ship the stack
Rewrites on React, Node.js, TypeScript and AI. A translated body is shown when it exists. If it does not, you see the English text and a note that says so.
Tagged: Streams
Understanding Node.js Streams: The Problem They Actually Solve
Why Node.js streams exist: data too big for memory, how piping connects a source to a destination internally, and what backpressure really does for you.
5 min readNode.js Streams Explained: Fixing Out-of-Memory File Crashes
Learn why loading entire files into memory crashes Node.js servers and how readable, writable, duplex, and transform streams fix it with backpressure.
9 min readNode.js Streams Beyond the Basics: Memory, Backpressure, and Real Failures
Learn how Node.js streams interact with Web Streams, measured memory savings with real benchmarks, and the production mistakes that surface only under load.
18 min read
FAQ
About these articles
Yes. Each piece is an original English rewrite prepared for this site. Structure and code examples follow the source material; prose is rewritten and checked for overlap before export.
English is the source. Another language is shown only when that translation body exists. A missing or empty translation stays in English, including on a localized URL.
New drafts land in the publish queue as they pass editorial checks. Running the site import picks up only new or changed slugs — nothing is duplicated.
Treat samples as illustrative. Validate against your stack and licences before production use. For delivery work, contact us with the brief.
Request a 24h estimate
Need the same stack in a production operator layer? Send the brief — estimate within 24 hours.