What We Build with Node.js
- APIs for web and mobile apps that serve and store data and call other services;
- real-time features: chats, notifications, online status and order tracking, where the server pushes updates to the client;
- middleware between systems: services that collect data from several APIs, transform it and pass it on;
- bots and event handlers for messengers, payment providers and CRMs;
- server-side page rendering for the Next.js and Nuxt frameworks.
When Another Technology Is a Better Choice
Node.js handles all requests on a single main thread, so long, heavy computation slows every user down. That decides where we recommend it and where we don't:
- if the product is built around data, analytics or machine learning, a backend in Python is the more natural choice;
- if you need maximum computational performance or a very high-load service with predictable memory usage, consider Go;
- if it's a typical website or online store on standard hosting, a PHP solution with an off-the-shelf CMS is often simpler and cheaper.
Express or NestJS
Express is minimalist, with few rules and a fast start, and fits small services, bots and intermediate APIs. NestJS enforces a clear structure and suits large products that several developers will work on for years. If a service was started in Express as a prototype and has grown without any structure, we don't rewrite everything at once; we gradually extract modules and cover the riskiest parts with tests.
Reliability and Security Built into Every Project
A Node.js server runs as a single long-lived process. If it crashes on an unhandled error, the website or app stops responding for everyone at once. That is why every project includes:
- automatic process restarts and multiple service instances, so one failure doesn't stop the whole system;
- server-side validation of all incoming data, even if the interface has already validated it;
- rate limiting, so a single client or bot can't overload the system;
- regular package scans for known vulnerabilities and an update plan;
- logs and error alerts in Sentry or a similar service, so developers learn about problems before customers do.
A New Service or an Existing One
A new service starts with a description of data, requests and external systems. From the outset we set up logging, error tracking and queues for long-running operations, because adding them later costs more.
An existing project is audited first: the Node.js version, package health and known vulnerabilities, memory usage under load, and how errors are handled. Often the server crashes from time to time because of a memory leak or an unhandled error in one request, and finding that cause is the first task. For systems with large user bases, we also offer high-load project support with monitoring and on-call coverage.
What to Prepare Before Kickoff
- The expected number of users and requests, and what data the server stores.
- A list of the external systems it must connect to, with API documentation.
- For an existing service: repository access, the current Node.js version and where it is hosted.
- Your preferred hosting, if you have one: a virtual server, a cloud or a platform such as Vercel.
What Affects Cost and Timeline
- Scope of logic: how many entities, roles and scenarios the server must handle.
- Integrations: the number of external systems and the quality of their documentation.
- Real time and load: whether live updates are needed and how many concurrent users are expected.
- Infrastructure: one server or several, redundancy, automated deployment.
- Code condition, for projects we take over for support.
We provide an exact estimate after discussing the task and, if needed, a short technical audit.
Frequently asked questions
How is Node.js different from NestJS? Node.js is the runtime that executes JavaScript on the server. NestJS is a framework that runs on top of Node.js and gives a large project its structure.
Can a Node.js service be connected to an existing PHP website? Yes. This is a common setup: the main site stays on PHP, while a chat, notifications or a standalone integration run on Node.js.
What hosting does Node.js run on? A virtual or dedicated server, the cloud, or platforms like Vercel for specific tasks. Standard shared hosting for PHP websites usually won't work.
Should we use TypeScript instead of JavaScript? For a service that will keep evolving, we recommend TypeScript: types help catch errors before runtime and make code changes safer. For a small bot or script, JavaScript is enough.
Do you take on projects built by another team? Yes. We start with an audit of the code and dependencies, then propose a plan: what to fix right away and what can be changed gradually.
Will you keep the server running after launch? Yes. We monitor the server, keep Node.js and packages up to date, and continue developing the product with you.
Why Promodex
Since 2015, Promodex has launched 750+ projects, including Bankroll. Backend, frontend, design and marketing are handled by an in-house team of 30+ people with no outside contractors. Before launch we load-test the service, watch memory usage and response times, and remove bottlenecks. You see what is being done and why from day one.