What To Build Next — and Where To Read
Going Further
Where to focus once you've finished the track. Resources, projects, ecosystems.
What you'll learn
- Pick a project to cement skills
- Know the canonical references
- Spot adjacent runtimes worth learning
You’ve covered Node from node --version to production. Here’s
where to go next.
Canonical References
- nodejs.org/api — the official API docs. Read sections as you use them.
- Express 5 docs — once you actually use Express in anger
- OWASP Top 10 — security
- The Twelve-Factor App — the practices most production Node apps follow
Project Ideas
Cement the fundamentals with a project:
- A typed REST API — Express + Zod + Drizzle + Postgres + Vitest
- A CLI tool —
parseArgs+fs/promises+ a npm publish - A real-time chat — WebSocket + Redis pub/sub for fan-out
- A job processor — BullMQ for image resizing or web scraping
- A small SaaS — auth + Stripe webhooks + admin endpoints
The third or fourth one is usually when Node “clicks.”
Adjacent Runtimes
JS server runtimes are no longer just Node. Worth knowing:
- Deno — TS-native, web-standard APIs, secure by default
- Bun — fast, all-in-one (runtime + pkg mgr + bundler + test runner)
- Cloudflare Workers / V8 isolates — edge-deployed JS, no Node — millisecond cold starts
All run a lot of Node code unchanged, with different trade-offs.
Frameworks Worth Trying
You learned Express. Once that feels natural:
- Fastify — faster, schema-driven, modern
- Hono — tiny, web-standard, runs everywhere
- NestJS — decorator/DI-heavy, Angular-like
- t3 / Next.js / Astro — full-stack with built-in server
Ecosystem Skills
Things that compound the longer you stay in JS:
- TypeScript (we have a whole track)
- A real ORM (Drizzle or Prisma)
- A queue (BullMQ)
- A test runner (Vitest)
- A real deploy (Render, Fly, your cloud)
The Mindset Shift
The biggest jump from “Node tutorials” to “Node in production”:
- Validate at the boundary (Zod). Trust inside.
- Async by default. Never block the loop.
- Crash fast. Don’t try to recover from programmer bugs.
- Measure before optimizing.
- Logs/metrics/traces from day one.
- Pick boring tech — Postgres, Express, Redis. Boring scales.
Congratulations
You can confidently build, ship, and operate a Node service. That’s the goal of this track. Now go build something.
↺ Back to the Start