Dissecting NodeJS - How it works under the hood
summary
Node is shown as V8 plus OS-facing C++ libraries—specifically V8+libuv+C++ bindings—with a concrete path for fs.readFile: JS calls internalBinding, hits node_file.cc, goes to libuv threadpool, then the callback queue and event loop. The talk demonstrates hidden classes and how hidden classes affect property order and performance, walks the Ignition→Turbofan bytecode→machine code pipeline replacing Crankshaft, and clarifies scheduling: the microtask job queue runs before macrotasks so promises execute before I/O callbacks, which can starve callbacks if misused.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:08JavaScript basics
- 3:40NodeJS architecture
- 6:50JavaScript engine
- 11:27Event loop explained
- 23:14V8 deep dive
- 33:15V8 compiler pipeline
- 38:51Bytecode execution
- 40:20Summary and resources
