Upvoting because its actually good advice (and someone has flagged it for some reason). Engineering is tradeoffs, the limiting factor in most databases is I/O;

Upvoting because its actually good advice (and someone has flagged it for some reason). Engineering is tradeoffs, the limiting factor in most databases is I/O; if you can shift your I/O around to do less of it with a stored procedure then you should probably do it, and having a breakout from SQL on the database itself can achieve that. The reason it scares DBAs is because while I/O is the primary constraint on a DB, everything else is also in finite supply, and people tend to forget how centralised and repeated a stored procedure can become. Especially if its on the hotpath. Developers have a habit of using stored procedures to make their application code easier to reason about rather than trying to minimise disk access. YMMV as with everything, but its a really nice capability to use rust for this, for the execution performance, quick start time and type safety.