Node.js.
Node.js is a JavaScript runtime built for I/O-bound server work: APIs, real-time connections and services that spend most of their time waiting on databases or other services. It is single-threaded with an event loop, which shapes both what it is good at and how it fails.
Where Node.js fits on a long engagement.
Node suits services whose work is mostly waiting. An API aggregating three upstream calls, a websocket layer holding thousands of idle connections, a webhook receiver — all cases where concurrency matters more than raw computation. It also lets a team share language and tooling with the browser, which is a genuine saving on a small team.
It fails in a recognisable way: one CPU-heavy operation on the event loop stalls every other request on that instance. Teams usually discover this under load rather than in review, which is why load behaviour is worth establishing early rather than at launch.
What an assigned team does with Node.js.
Node services tend to multiply. What starts as one API becomes four small services because they are cheap to create, and after two years nobody can say which of them are load-bearing. An assigned team that was there when each was written answers that question from memory rather than from archaeology.
Where the constraint turns out to be the deployment and observability of those services rather than writing them, that is a different assignment: DevOps as a service capacity on the same agreement, moving at the monthly cycle.
What we use Node.js for.
- An API gateway over older systems One well-shaped interface in front of several legacy services, without touching the systems underneath.
- Real-time features Notifications, presence and live updates, where holding many idle connections cheaply is the requirement.
- One language across the stack A small team sharing conventions and utility code between browser and server rather than maintaining two ecosystems.
How Node.js capacity is assigned.
Node capacity is assigned under outsource software development services, most often alongside frontend work on the same agreement rather than as a separate engagement.
Tell us what your roadmap needs Node.js for.
A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.