Own product · Taxi dispatch SaaS
TaxiDex
My own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
Freelance · Node.js
I am one senior engineer who builds and runs Node.js back ends: REST APIs, background jobs, live sockets and the Linux servers they sit on. My own product, TaxiDex, is a Node.js API with more than 1,000 routes that I operate in production. I join your team remotely, by the project or month by month.
The process crashed, was never restarted or listens somewhere nginx does not look. I find which one from the logs before touching the configuration.
The step-by-step fixUsually an old process that never exited, or two process managers fighting over one app.
The step-by-step fixLeaked file handles and sockets show up as EMFILE long before the server runs out of CPU.
The step-by-step fixA proxy timeout closes idle WebSockets, and clients reconnect in a loop that looks like a bug in the app.
The step-by-step fixAn emitter with no error listener is enough to stop every request that was in flight.
The step-by-step fixA dependency went ESM-only and the build no longer loads it. There is a correct way through that does not pin old versions forever.
The step-by-step fixEither. I can own the back end outright, or join your team, review code and take the hard parts myself.
AdonisJS for my own SaaS, NestJS and Express on other products. I work in the framework you already have rather than asking you to switch.
Yes. I start with a short written review of the code, the deploy process and the risks, so you know what you have before I change anything.
I raise the limit where the service starts and stop opening thousands of files at once. I wrote a fix page on the EMFILE error that explains both.
With a shared task board, short written updates and one fixed overlap call each week for the decisions that need a conversation.
Proof
From the fix library
HTTP 502: Bad gatewayApplication Load Balancer returns 502 for a Node.js targetMissing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1The AWS SDK in Node.js cannot find any credentialsError: Cannot find module 'canvas'Chart.js on Node.js fails because the canvas module is missingError: connect ECONNREFUSED 127.0.0.1:3306Node.js in Docker Compose cannot reach MySQL on 127.0.0.1:3306ERR_DLOPEN_FAILEDNode.js cannot load a compiled .node addonERR_OSSL_EVP_UNSUPPORTEDnpm run start crashes with ERR_OSSL_EVP_UNSUPPORTED after a Node.js upgradeMonth by month
Next step
A discovery call within 48 hours, and a kickoff typically inside two weeks.