V8 isolate
A separate instance of the V8 engine with its own heap and garbage collector; objects in one isolate cannot be seen from another.
In more detail
Every worker thread gets its own isolate, which is why data must be copied or explicitly shared between threads. Creating one costs time and memory, which is one reason worker threads are best reused.
Related terms
- Edge runtime — A lightweight Next.js runtime based on V8 isolates and standard Web APIs, which starts almost instantly but cannot use most Node.js APIs.
- cold start — The extra delay when a platform must start a fresh copy of your code or server before it can serve the first request.
- V8 — Google's open-source JavaScript engine, used by Chrome and Node.js to parse, compile and run JavaScript.
- worker threads — The Node.js module for running JavaScript in parallel threads inside one process, each with its own V8 isolate and event loop.
- heap — The area of memory where a program stores objects whose size or lifetime is not known in advance, typically reclaimed by a garbage collector.
Taught in
- Runtime Environments: Node.js vs Edge Runtime Choice — Next.js 15 & Modern App Router Architecture
- Child Processes: spawn, execFile, fork & IPC — Node.js Internals & Backend Services
- Worker Threads: worker_threads & SharedArrayBuffer — Node.js Internals & Backend Services
- Thread Pooling: Piscina & CPU-Bound Workload Pools — Node.js Internals & Backend Services