Node.js

Node.js is a cross-platform runtime environment that allows developers to create server-side applications using JavaScript. It uses a non-blocking, event-driven I/O model that makes it efficient and lightweight. Node.js is commonly used for building web applications, APIs, and real-time applications.

Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.

Content type

Technology

Technical building block: can be automated, integrated, or operated.

Classification level

Element

Concrete cog in the system that works inside larger relationships.

Available perspectives

Open this building block directly in an already curated view.

360°

In brief

Node.js – in brief

Node.js is an open-source JavaScript runtime that executes JavaScript outside the browser on the V8 engine.

Where does it come from?

Ryan Dahl introduced Node.js in 2009 to enable event-driven, non-blocking server programs in JavaScript. The original project grew into a cross-platform runtime with a large package ecosystem.

The mental model

A process loads JavaScript and handles events through an event loop. Non-blocking APIs delegate I/O to the operating system or a worker pool; callbacks, promises, and async/await return results to application code.

Key building blocks

Runtime

Node.js provides APIs and an engine so JavaScript can run as a program.

Event loop

An event model coordinates results without making the main thread wait for I/O.

Modules

CommonJS and ECMAScript modules structure code and dependencies.

When is it useful?

Node.js fits APIs, tools, and I/O-heavy services. CPU-intensive work, process isolation, failure boundaries, dependencies, and runtime versions must match the workload and operating model.

Node.js documentation Official Node.js GitHub repository Node.js Tutorials