Node.js & ExpressWhen you ask AI to build a backend, there is a good chance it reaches for Node.js. It generates an Express server, wires up some routes, and hands you working code. But do you know what Node.js actually is, why it was created, and when it is the wrong choice? Understanding the runtimeWhat is runtime?The environment that runs your code after it's written. Some languages need a runtime installed on the machine; others (like Go) bake it into the binary. beneath the code AI generates is the difference between shipping confidently and shipping blindly.
JavaScript outside the browser
For most of JavaScript's history, it could only run inside a web browser. The browser provided the runtimeWhat is runtime?The environment that runs your code after it's written. Some languages need a runtime installed on the machine; others (like Go) bake it into the binary. environment, the engine that reads and executes JavaScript code. In 2009, Ryan Dahl took Chrome's V8What is v8?Google's JavaScript engine that compiles JavaScript to native machine code - it powers both Chrome and Node.js. JavaScript engine and wrapped it in a standalone program that could run on a server. That program is Node.js.
| Concept | Browser | Node.js |
|---|---|---|
| JavaScript engine | V8 (Chrome), SpiderMonkey (Firefox) | V8 |
| Can access the DOM | Yes | No |
| Can access the filesystem | No | Yes (fs module) |
| Can create HTTP servers | No | Yes (http module) |
| Can run shell commands | No | Yes (child_process module) |
| Global object | window | global / globalThis |
Node.js does not add new syntax to JavaScript. The language is identical. What changes is the environment: instead of document.querySelector(), you get fs.readFile(). Instead of fetch() from a browser tab, you get http.createServer() that listens for incoming requests.
Why one language matters
Before Node.js, a typical web team used JavaScript for the frontend and a completely different language (PHP, Ruby, Java, Python) for the backend. This meant two toolchains, two sets of conventions, and developers who could only work on half the stack.
Node.js changed that. A single developer can write the React component that renders a form and the APIWhat is api?A set of rules that lets one program talk to another, usually over the internet, by sending requests and getting responses. endpointWhat is endpoint?A specific URL path on a server that handles a particular type of request, like GET /api/users. that processes the submission, in the same language, sometimes sharing the same validation logic between client and server.
This is exactly why AI defaults to Node.js so often. The training data is full of JavaScript, and Node.js lets AI generate a complete full-stack application in one language without switching contexts.
Single-threadedWhat is single-threaded?A model where one main execution thread handles all work - Node.js uses this with an event loop to handle many requests concurrently. and event-driven
Node.js runs your JavaScript on a single thread. This sounds like a limitation, but it is actually a design choice that makes Node.js excellent at a specific category of work: I/O-heavy tasks.
Most web servers spend their time waiting, waiting for a database query to return, waiting for a file to be read, waiting for an external APIWhat is api?A set of rules that lets one program talk to another, usually over the internet, by sending requests and getting responses. to respond. Node.js handles this by never blocking. When it starts a database query, it does not sit idle waiting for the result. It moves on to handle the next request, and when the database responds, a callbackWhat is callback?A function you pass into another function to be called later, often when an operation finishes or an event occurs. fires to process the result.
// Node.js does NOT wait here - it moves on immediately
const data = await fs.promises.readFile('config.json', 'utf-8');
// This line runs only after the file is actually read
console.log(data);This event-driven model means a single Node.js process can handle thousands of concurrent connections, as long as the work is mostly waiting for I/O. A Node.js server handling 10,000 simultaneous API requests that each query a database is perfectly reasonable.
But ask that same server to resize 10,000 images, and it collapses. Image resizing is CPU work, it blocks the single thread, and every other request waits in line. This is the fundamental trade-off you need to understand when reviewing AI-generated Node.js code.
Node.js is not a framework
This is a distinction AI-generated code often blurs. Node.js is a runtimeWhat is runtime?The environment that runs your code after it's written. Some languages need a runtime installed on the machine; others (like Go) bake it into the binary., it provides the ability to run JavaScript and gives you low-level building blocks like http, fs, path, and crypto. It does not provide routing, middlewareWhat is middleware?A function that runs between receiving a request and sending a response. It can check authentication, log data, or modify the request before your main code sees it., or request parsing out of the box.
| Layer | What it is | Examples |
|---|---|---|
| Runtime | The engine that executes JavaScript | Node.js, Deno, Bun |
| Framework | Adds structure, routing, middleware on top of the runtime | Express, Fastify, Koa, Hapi |
| Meta-framework | Full-stack framework with SSR, routing, bundling | Next.js, Nuxt, Remix |
When AI generates a Node.js server, it almost always imports Express or another framework immediately. The raw http moduleWhat is module?A self-contained file of code with its own scope that explicitly exports values for other files to import, preventing name collisions. is rarely used directly in production code. But knowing that the framework sits on top of Node.js, and that Node.js itself handles the event loopWhat is event loop?The mechanism that lets Node.js handle many operations on a single thread by delegating slow tasks and processing their results when ready., file I/O, and process management, helps you debug problems that live below the framework layer.
When Node.js is the right choice
Node.js shines for real-time applications (chat, live updates), APIWhat is api?A set of rules that lets one program talk to another, usually over the internet, by sending requests and getting responses. servers that mostly proxy data between databases and clients, microservicesWhat is microservices?An architecture where an application is split into small, independently deployed services that communicate over the network, each owning its own data. that handle high request volumes with low latencyWhat is latency?The time delay between sending a request and receiving the first byte of the response, usually measured in milliseconds., and tooling like build scripts, CLIWhat is cli?Short for Command Line Interface. A tool you use by typing commands in the terminal instead of clicking buttons. tools, and development servers.
It struggles with CPU-intensive computation, applications that need true multi-threading out of the box, and workloads where memory usage per connection matters (Node.js is more memory-hungry than Go or Rust).
The Node.js ecosystem
Node.js comes with npm (Node Package Manager), which gives you access to over 2 million packages. This ecosystem is both a superpower and a liability, you can find a package for almost anything, but choosing the right one (and avoiding abandoned or insecure ones) is a skill in itself. The next lessons cover npm in depth.
The key takeaway: Node.js is a powerful runtimeWhat is runtime?The environment that runs your code after it's written. Some languages need a runtime installed on the machine; others (like Go) bake it into the binary. for I/O-heavy server work. When AI generates a Node.js backend for you, your job is to verify that the workload actually fits the single-threadedWhat is single-threaded?A model where one main execution thread handles all work - Node.js uses this with an event loop to handle many requests concurrently., event-driven model, and to push back when it does not.