An API receives a PDF, asks a model to extract the fields, and returns the result. On your laptop it works: the model takes a few seconds, the response arrives, everyone is happy. The trouble starts when the second, the tenth and the hundredth user upload files at the same time.
People often describe this as "the API freezes." In Node.js that's only half true, and the other half changes the fix.
The event loop is (usually) not the villain
When your code await s an HTTP call to an AI provider, Node.js does not sit and wait. The official Node.js guide explains that the event loop orchestrates client requests, and that the server stays fast as long as the work for each client is small. A network call is I/O: the process keeps serving other requests while the response is in flight.
The event loop really does block when the work is CPU-bound inside your own process: local OCR, image resizing, PDF generation, running a small model in JavaScript.β¦