Node.js from
the inside out.

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

Every published chapter is free to read online.

RuntimeMemoryProcessesNetworkingProduction

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.

Build a complete mental model

See every chapter

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.

“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 writes NodeBook for developers who are ready to stop guessing about the systems underneath their applications.