One thing that I found interesting, is that Bun's FFI interfaces are blocking only... Deno's supports having the execution and responses async, which can help. I wound up having to use koffi for Node and Bun because of this limitation in order to improve performance.
I do wish that koffi's interfaces were supported in the box for Node, though NAPI is pretty stable, I feel that a straight up FFI approach can be better for some types of library integrations.
On the article itself, it's really conflating a lot of issues that can be performance issues that are well outside your runtime itself. Database utilization, tuning and even connections in environments where you may be horizontally scaling can be a serious issue.
Beyond this, database drivers are not all the same... depending on the driver itself and how connections are handled, for the promise.all, it could be serializing the requests on a single connection, or it could be acquiring several connections from the same pool. Hard to know for sure. That doesn't even get into connection gateways for things like PostgreSQL, CRDB, etc. that have expensive connections, which can be problematic combined with worker services like Lambda, Cloudflare or Vercel, where you may not want to have larger pools of connections. Which is an entire other area not even discussed.
tracker1 1 day ago. link 1 point ▲ ▼