Node.js fromthe inside out.

NodeBook explains what happens underneath your JavaScript, from the event loop and memory to processes, networks, and production systems.

Start readingRun the event loop
Every published chapter is free to read online.
Raw ModeSee the build →

Build your own backend framework from raw TCP. Zero dependencies.

$69.99$99.99Get full accesslifetime, one payment

Plus every NodeBook volume, PDF and EPUB editions, and every Runtime Lab.

50framework lessons live
102senior + staff interview chains
393follow-up questions
40AI hallucination drills
6broken repos to debug
8system design scenarios

The event loop, running in this tab.

Queue callbacks, cut the line with process.nextTick, starve the loop with promises, or block the thread outright. The dial, the console, and the delay trace are all driven by this page’s own main thread.

Phasepoll
Iteration0
Queued0
Loop delay0.0 ms
Now runninghover the dial to see each phase
pollRetrieve new I/O events and run their callbacks.
Press a key, or 1 – 8 on your keyboardor click a phase on the dial
Console · execution orderstdout
Each key queues a callback. Its line prints here the moment it actually runs.
Measured loop delay in this tab, last 6 secondspeak 0 ms

Most Node.js material stops at the API. NodeBook keeps going until the behavior makes sense.

Learn the model behind the code, then use it to explain timing bugs, memory growth, stalled streams, failed requests, and the tradeoffs inside real backend systems.

−01RuntimeV8 · libuv
−02Memoryheap · buffers
−03Processessignals · stdio
−04NetworkingTCP · TLS · HTTP
−05Productiondebug · shutdown

Build a complete mental model

See every chapter
01
The Node.js runtimeFollow JavaScript from your source file into V8, libuv, and the operating system.
02
Buffers and binary dataUnderstand bytes, encodings, memory views, and the data underneath every protocol.
03
Streams and backpressureMove large inputs through bounded memory without letting fast producers overwhelm slow consumers.
04
Files, processes, and the OSSee what really happens when Node.js opens a file, starts a process, or talks to the kernel.
05
Async control flowReason about timers, microtasks, promises, cancellation, concurrency, and failure.
06
Networking and HTTPTrace a request through TCP, TLS, parsing, routing, response writing, and connection reuse.

Read less documentation. Understand more of the system.

01

Start with the mechanism

The API is only the surface. Each chapter follows the work into the runtime and the operating system so the result stops feeling magical.

02

Prove it with code

Small experiments make timing, memory, and network behavior visible. You can run them, change them, and test your own mental model.

03

Use it in real systems

The material ends where production begins: debugging, observability, graceful shutdown, performance, and architecture.

A growing library for serious backend work.

NodeBook is organized as a set of focused volumes. Start with the runtime, continue through networking, then move into data, security, production engineering, and architecture as new volumes are published.

Open the reader
I

Runtime Foundations

Architecture, buffers, streams, files, processes, modules, and asynchronous control flow.

Available
II

Networked APIs

TCP, HTTP, TLS, API design, real-time systems, and the path from socket to response.

Available
III to VII

The complete backend path

Native work, data and state, security, production engineering, and system architecture.

In progress

Read online.Keep it offline.Build it by hand.

The website stays open for reading. Digital Edition gives you the books in EPUB and PDF. Raw Mode adds the Runtime Labs, the backend framework build, and the complete practice system.

Read for freeCompare the two options
“I wanted a Node.js book that stayed close to the code and still explained what the runtime was doing. So I made one.”
Ishtmeet Singh

Ishtmeet Singh writes NodeBook for developers who are ready to stop guessing about the systems underneath their applications.