Learning paths · Skills · Intermediate

Node.js: how the server side runs

What happens between your JavaScript and the operating system: the loop's phases, its private queues, the thread pool, streams, and threads of your own.

0 of 8 done

The map

Not started
In progress
Done
Builds on

01From JavaScriptRules shared with browsers

02Node's loopPhases, queues, the pool

03Doing more at onceStreams and more cores

04Next: system designSame ideas, at service scale

BackpressureLibrary ↗Streams' highWaterMark and 'drain', between services: bound every buffer, let the slow side set the pace.

BulkheadLibrary ↗The thread pool is one shared resource. Bulkheads give each kind of work its own.

Competing consumersLibrary ↗Workers taking jobs from one queue, across machines instead of threads.

01From JavaScriptRules shared with browsers0/3
02Node's loopPhases, queues, the pool0/3
03Doing more at onceStreams and more cores0/2
04Next: system designSame ideas, at service scale

Topics shared with the JavaScript path keep the same progress on both maps.

Where this path leads