Platform / Node.js
One language across the stack
APIs, workers and scheduled jobs on the same runtime as the front end, so one engineer can follow a request from click to database.
At a glance
Used in
New capability
Services
3
Handover
Your repo, day one
01 / What we build with it
Where Node.js earns its place.
01
Typed HTTP APIs
Contracts generated from the schema, not written twice.
02
Background workers
Queues, retries and dead letters, with the failure path designed first.
03
Scheduled jobs
Cron work that reports when it did not run, not only when it did.
04
Streaming and sockets
Where the interface has to update itself.
02 / Honestly
Why this, and when not.
Why we choose it
Sharing a language with the browser removes an entire translation layer, and with it a category of bug nobody enjoys finding.
When we would not
CPU-bound work: heavy numerics, model inference, constraint solving. That belongs in Python or Go, called from here.
03 / Where it fits
Services built on Node.js.
Taking projects for Q4
Building something with Node.js?
A 45-minute technical call with the engineer who would lead the build. You leave with a scope sketch either way.