About NodeBook

A backend engineering book written through Node.js.

The reason NodeBook exists is that most Node material stops at API usage. The book keeps going - runtime internals, protocol mechanics, data systems, queues, security, observability, deployment, and architecture.

Read the book Get labs and files

Why NodeBook

The book is for working developers. It assumes you can write JavaScript already, then spends time on the parts that show up when backend systems run under load.

The runtime comes first

The book follows what Node does across V8, libuv, buffers, streams, modules, async queues, sockets, and HTTP.

Failure paths stay in

Backpressure, partial reads, memory growth, descriptor pressure, module hazards, process exits, and operational edge cases are part of the text.

Backend pieces connect

Buffers lead into streams. Streams lead into networking. Networking leads into HTTP. Later chapters carry that thread into data, queues, security, and production work.

Labs force the build

Node Runtime Labs turn runtime mechanics into local projects with commands, fixtures, expected output, reports, and checks.

Free online reading

The public book stays free online. Paid products add local files, slides, cheatsheets, and project labs.

Local files

Digital Bundle packages EPUB, PDFs, visual slides, cheatsheets, and file updates for readers who want a local copy.

Reader notes

Early feedback from people reading NodeBook for internals, debugging, and self-study.

Free and serious

Thanks for keeping this resource free and accessible. Expensive courses are out of reach for a lot of people, and this gives us a real path into Node internals.

Internals without filler

I wanted something that explains how Node works at runtime, not another API tour. This is the kind of material I needed.

Examples that land

The explanations are clear and the examples make sense. It helped me connect day-to-day Node code to what the runtime is doing.

Written byIshtmeet Singh

About the author

I've worked with Node.js since 2014 on real-time applications, backend services, and performance-sensitive systems. NodeBook came from reading runtime behavior, debugging production issues, and writing down details scattered across docs, source, talks, and incident notes.

My systems work in Rust and C++ changed how I read Node.js. It made memory ownership, native I/O, queues, process state, file descriptors, streams, and network behavior harder to ignore. That perspective runs through the book and the labs.

GitHub Contents

Get emails when new public chapters, Node Runtime Labs, and digital files ship.