0 of 2 done
The platform underneath every JS backend framework. Notes here are runtime-level, not framework-level.
- Environment Validation — failing fast on bad config at boot
- Error Handling — the four error channels and why
uncaughtExceptionisn’t recovery
The runtime facts that matter most
- The event loop is single-threaded. Any sync work blocks every pending request → the signature p99 spike with flat p50. → p99 debugging
- libuv’s thread pool defaults to 4 (
UV_THREADPOOL_SIZE) and servesfs, DNS, and some crypto — network I/O does not use it. worker_threadsfor CPU,cluster/replicas for cores. They solve different problems.Buffer.allocnotnew Buffer— the deprecated form returned uninitialised memory and was a type-confusion trap. → Q2
→ Full depth in the Node runtime interview bank, which was written from a real interview.
Related
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering