How to Scale a Node.js API from 100 to 1M Requests
Each scaling tier exists to remove one specific bottleneck. Here is which bottleneck, in what order, and what each fix costs you.
What I have learned building production systems — architecture, scale, reliability and AI pipelines. Each article states plainly whether it describes something I built, something demonstrated on this site, or a reference design.
Each scaling tier exists to remove one specific bottleneck. Here is which bottleneck, in what order, and what each fix costs you.
All articles
Each scaling tier exists to remove one specific bottleneck. Here is which bottleneck, in what order, and what each fix costs you.
The demo is a vector search and a prompt. The production system is eight components, and most of the engineering is in the seven that are not the model.
When to do the work inside the request, when to queue it, and the four things that make a queue safe to retry.
Three isolation models, how to pick one, and why the dangerous bug is always a query somebody forgot to scope.
Every external dependency will fail. Timeouts, breakers, backoff and a defined degraded state are the four things that decide whether that becomes your outage.
Read-only mode, buffered writes and a rehearsed failover turn a database outage into degraded service instead of a dead product.
Rendering strategy is a per-route decision, not a per-app one. Marketing pages, dashboards and documentation each want something different.
Working on something like this?
If any of these problems look like yours, the fastest way forward is a short technical conversation.