Streams ni nini katika Node.js na ni lini unapaswa kuzitumia?

Question

Accepted Answer

**Streams** huchakata data **sawa na sawa, kwa sehemu**, badala ya kuokoeza kila kitu katika kumbukumbu mara moja. Hii inazifanya muhimu sana kwa data kubwa (faili kubwa, uwanja wa mtandao) ambapo kusambaza kila kitu lingekumea kumbukumbu.

## Tatizo linalosuluhishwa na streams

```js
// ❌ loads the ENTIRE file into memory — crashes on a 10GB file
const data = await fs.promises.readFile("huge.csv");
process(data);

// ✅ stream it — constant memory, processes chunk by chunk
fs.createReadStream("huge.csv")
  .pipe(transform)
  .pipe(fs.createWriteStream("out.csv"));
```

Kwa streams, matumizi ya kumbukumbu yanabaki thabiti bila kujali ukubwa wa faili — unashughulikia sehemu moja kwa wakati.

## Aina nne za stream

```text
Readable  → source you read FROM (fs.createReadStream, http request)
Writable  → destination you write TO (fs.createWriteStream, http response)
Duplex    → both readable & writable (TCP socket)
Transform → modify data as it passes through (zlib gzip, encryption)
```

## pipe — kuunganisha streams

```js
import { createReadStream, createWriteStream } from "fs";
import { createGzip } from "zlib";

// read → compress → write, all streaming, low memory
createReadStream("file.txt")
  .pipe(createGzip())            // Transform: compress on the fly
  .pipe(createWriteStream("file.txt.gz"));
```

`pipe` inaunganisha kile kinachoweza kusomwa na kile kinachoweza kuandikwa (na mabadiliko kati yake), inasimamia mtiririko otomatiki — njia inayofaa ya kutunga streams.

## pipeline — pipe na uongezaji wa kawaida wa hitilafu

```js
import { pipeline } from "stream/promises";

await pipeline(
  createReadStream("in.txt"),
  createGzip(),
  createWriteStream("out.gz")
); // ✅ cleans up all streams on error/completion (pipe alone leaks on errors)
```

`pipeline` inapendekezwa zaidi kuliko `.pipe()` iliyounganishwa kwa sababu inaeneza makosa na kusafisha kila stream vizuri.

## Mahali ambapo streams huonekana

```text
✓ HTTP request/response bodies (req and res ARE streams)
✓ File reading/writing, file uploads/downloads
✓ Compression (zlib), encryption (crypto)
✓ Database cursors, large query results
✓ Real-time data processing, video streaming
```

## Wakati wa kusikitishwa SI kazi

```text
Small data that fits comfortably in memory → readFile/simple buffering is simpler.
Streams add complexity; use them for LARGE or continuous data.
```

## Kwa nini hii ni muhimu

Streams ni sifa inayofafanua Node.js kwa ajili ya uongezaji wa **ufanisi wa kumbukumbu** wa data kubwa au iliyoendelea — tofauti kati ya programu inayoanguka kwa upload kubwa na ile inayoshughulikia saizi yoyote na kumbukumbu imara.

Kuelewa aina nne, muundo wa `pipe`/`pipeline` (na kwa nini `pipeline` ni salama zaidi) na kwamba ombi la HTTP/majibu ni streams wenyewe ni muhimu kwa ajili ya kujenga huduma inayofanana ya usindikaji wa faili, usindikaji wa data na proxy katika Node.