What metrics prove Streams and Backpressure is healthy in prod?

Answers use simple, clear English.

Quick interview answer

Prove Streams and Backpressure is healthy with latency (p50/p95/p99), error/saturation rates, and queue/event-loop lag — not just CPU. Context: Use Streams and Backpressure as the core idea. Example shape: ETL job pipes HTTP download → gzip transform → S3 upload without loading entire file into RAM..

Detailed answer

Production health signals for Streams and Backpressure: • Latency: p50/p95/p99 of the critical path that uses Streams and Backpressure. • Errors: failure rate, timeouts, and retry storms. • Saturation: queue depth, event-loop delay, thread/pool utilization. • Business SLIs: request success and user-visible freshness where relevant. Trade-off lens: Pros: Constant memory for large files; composable pipeline with pipe(). Cons: Error handling across piped streams needs explicit destroy/abort logic. Explain thresholds + alerts, then how you triage. Parent context: Use Streams and Backpressure as the core idea. Example shape: ETL job pipes HTTP download → gzip transform → S3 upload without loading entire file into RAM..

Full explanation

Good answers name measurable signals and what “bad” looks like for Streams and Backpressure. Readable pushes data; Writable signals backpressure when internal buffer exceeds highWaterMark. Respect drain event before resuming writes to avoid memory blowup.

Follow-up questions

Only answered follow-ups are shown — click to open with full answers

Parent context — Streams and Backpressure

Use Streams and Backpressure as the core idea. Example shape: ETL job pipes HTTP download → gzip transform → S3 upload without loading entire file into RAM..

View full parent question →

#node-streams-backpressure#junior