Node.js is a runtime that lets you execute JavaScript outside the browser — most importantly on a server — so the same language you use for the frontend can also power the backend. For years JavaScript lived only inside web browsers, with no way to run on its own. Node.js changed that by taking V8 — the fast JavaScript engine from Google Chrome — and packaging it as a standalone program you launch from the command line. The language is exactly the same: a for loop, a function, an array all behave identically. What changes is the environment around the code, and that swap is the whole point. In the browser, JavaScript talks to the page: document, window, the DOM. None of that exists on a server, so in Node.js those browser APIs are gone. In their place, Node gives your code what a server actually needs: The file system — read and write files on disk The network — open sockets, listen for HTTP requests OS features — environment variables, processes, system info Two design choices make Node well-suited to servers. It is event-driven with non-blocking I/O, meaning a single thread can juggle thousands of waiting connections instead of stalling on each one (the basis for the event loop covered separately). And because it runs plain JavaScript, the frontend and backend can share one language and even share code. That versatility shows up everywhere Node is used: web servers and APIs, command-line tools, build tools like Webpack and Vite, and even desktop apps via Electron. Memory tip: same language, different toolbox — keep your JavaScript knowledge, swap document/window for files, network, and the OS. Go deeper: Node.js: Introduction to Node.js — the official "what is it" guide, V8 + non-blocking I/O, with a runnable HTTP-server example. Wikipedia: Node.js — history and architecture of the runtime.

Quiz Entry - updated: 2026.07.05

What is Node.js?

Node.js is a runtime that lets you execute JavaScript outside the browser — most importantly on a server — so the same language you use for the frontend can also power the backend.

For years JavaScript lived only inside web browsers, with no way to run on its own. Node.js changed that by taking V8 — the fast JavaScript engine from Google Chrome — and packaging it as a standalone program you launch from the command line. The language is exactly the same: a for loop, a function, an array all behave identically. What changes is the environment around the code, and that swap is the whole point.

In the browser, JavaScript talks to the page: document, window, the DOM. None of that exists on a server, so in Node.js those browser APIs are gone. In their place, Node gives your code what a server actually needs:

The file system — read and write files on disk
The network — open sockets, listen for HTTP requests
OS features — environment variables, processes, system info

Two design choices make Node well-suited to servers. It is event-driven with non-blocking I/O, meaning a single thread can juggle thousands of waiting connections instead of stalling on each one (the basis for the event loop covered separately). And because it runs plain JavaScript, the frontend and backend can share one language and even share code.

That versatility shows up everywhere Node is used: web servers and APIs, command-line tools, build tools like Webpack and Vite, and even desktop apps via Electron.

Memory tip: same language, different toolbox — keep your JavaScript knowledge, swap document/window for files, network, and the OS.

Go deeper:

Node.js: Introduction to Node.js — the official "what is it" guide, V8 + non-blocking I/O, with a runnable HTTP-server example.
Wikipedia: Node.js — history and architecture of the runtime.

From Quiz: WEBT / Backend Development | Updated: Jul 05, 2026