0 of 41 chapters written · 3 levels planned
Node.js
The runtime on the server side
Not written yet
The other runtime around the same engine: modules, streams, the event loop phases, and how I/O really works. Beginner through advanced, laid out the same way as the rest of the shelf — the shelf is up, each section opens the moment it's written.
The plan
- chapters planned
- 41
- levels
- 3
- chapters written
- 0
What is planned, level by level
Every stop below is an outline for now. Open one to see what it will cover.
Beginner
“I can build a working server.”
9 sections
- soon
- soon
- soon
- soon
Intermediate
“I can ship a real backend.”
15 sections
- soon
Advanced
“I can reason about the runtime under load.”
17 sections
- soon
- soon
- soon
- soon
- soon
- soon
Meanwhile
Nothing here is written yet, but these are.
Three honest notes
The event loop shows up twice on purpose — once as "here's the shape" in beginner, once as "here's why your app actually stalled" in advanced, with real profiling in between.
Databases, auth and testing sit in the intermediate tier because that's when most real Node work actually starts — a server that can't persist or verify anything isn't a backend yet.
Native addons and building a custom renderer for Node's internals are the deepest, rarest layer — most working backend engineers never need them, but the advanced tier doesn't skip them.