Node.js

0 questions

The JavaScript runtime most backend JS jobs mean by 'server-side JS': one event loop, non-blocking I/O, npm, streams, and an escape hatch to worker threads. Interviewers dig in because Node rewards you for knowing what it does while your callback is waiting.

questions

no questions here yet

this part of the tree is still being written

>

0 questions in this topic or below it

browse the rest of Server Runtimes & Process Management →

explore

Event Loop and Async Modelempty
- Loop Phases and libuvempty
- process.nextTick and Microtasksempty
- Timers vs setImmediateempty
- Blocking the Loop and Event-Loop Lagempty
Module Systems and npmempty
- CommonJS at Runtimeempty
- ESM in Node and Interopempty
- Resolution and package.json exportsempty
- Loader Hooks and Running TypeScriptempty
Streams and Buffersempty
- Stream Types and Reading Modesempty
- Backpressure and pipeline()empty
- Implementing Custom Streamsempty
- Buffers and Binary Dataempty
File System and Networkingempty
- Async File-System Patternsempty
- HTTP and HTTP/2 Serversempty
- HTTP Clients and Connection Poolingempty
- TCP, UDP, and DNSempty
Worker Threads and Clusteringempty
- worker_threadsempty
- child_process and Subprocessesempty
- cluster Moduleempty
- Choosing Threads, Processes, or Replicasempty
Error Handling and Observabilityempty
- Error Conventions and Propagationempty
- Process Events and Crash Policyempty
- Graceful Shutdownempty
- Async Context and Diagnosticsempty