When we use Node.js.
For application backends and the APIs that serve them. For services that need to keep many connections open at once — notifications, real-time updates, continuous communication with devices or other systems. And for integrations between systems that talk over HTTP, where the work is mostly waiting and routing.
This is where it pays off: many things waiting together, little computation for each one.
The technologies we work with
The technologies we work with
When we do not use it
When we do not use it
When the work is computation. Heavy processing on large volumes, data transformations, analysis: Node is not the right tool there and we use Python. When memory control and tight, predictable response times are needed, we use Rust.
It is not a hierarchy: these are tools that solve different problems. A well-built system uses more than one.
What we have used it for
What we have used it for
BuildMarketplace
Sailsquare — 5 years on the platform, alongside their team.
5 yearsActive
[REDACTED]
ScalePrediction Markets
Prediction market — order-matching engine.
3 yearsActive
The way we work is the same across technologies: peer review before release, separate environments, and automated pipeline checks. How we work