Node.js
JavaScript on the server: modules, files, HTTP.
Node.js is taught here in 13 lessons, running from Node.js: getting started through to Security, performance and deployment. Each lesson takes one topic, shows the working code, and links onward to the next, so the course can be read straight through in order.
| Track | Back-end Development |
| Lessons | 13 |
| Level | Beginner to intermediate |
| Reading time | about 3 hours |
| Prerequisites | None beyond being able to open a text editor |
Lessons
- Node.js: getting startedRunning JavaScript outside the browser, the event loop that makes it scale, and the module systems you will meet.
- npm, packages and scriptspackage.json, semantic versioning, lockfiles, and the scripts and workspaces that keep a project reproducible.
- Files and paths in NodeAsync file I/O with promises, streams for large data, and building paths that work on every platform.
- Building an HTTP serverA server with no framework, routing by hand, reading the body, and when to reach for Express-style libraries.
- Modules, ESM and CommonJSimport versus require, the package.json type field, conditional exports, and how the two module systems talk to each other.
- Events, streams and buffersEventEmitter patterns, readable, writable and transform streams, backpressure, and the byte-level rules of Buffer.
- Async patterns, timers and the event loopPromises and async/await discipline, the timer functions, scheduling order between nextTick, microtasks and setImmediate, and cancellation.
- Configuration, environment and CLI argumentsprocess.env, env files and --env-file, a config shape that fails fast, and parsing command-line arguments properly.
- Errors, logging and debuggingCustom error classes with cause chaining, exit codes that mean something, structured logs, and the built-in inspector.
- Testing with the built-in test runnernode:test and assert, suites and subtests, mocks and fake timers, watch mode, coverage and global setup.
- Databases, HTTP clients and external servicesfetch with timeouts, retries and idempotency, connection pooling, migrations and transaction boundaries.
- Worker threads, child processes and clusteringMoving CPU-bound work off the event loop, running other programs safely, scaling across cores, and shutting every process type down cleanly.
- Security, performance and deploymentValidate input at the boundary, limit and time every call, profile before optimising, and ship a small container that shuts down cleanly.
More in Back-end Development
PHP Java HTTP Go Rust Spring Boot Laravel Ruby GraphQL
FAQ
How long does the Node.js course take?
It has 13 lessons, about 3 hours of reading. Expect roughly twice that if you type out and run every example.
Do I need prior experience for Node.js?
No. This is the first course in Back-end Development, so it starts from the beginning and assumes no background.
What should I read after Node.js?
Continue with PHP (13 lessons), the next course in Back-end Development.
Last refreshed 2026-09-18.