But seriously, I don't know. It seems like it trades development speed for things that just aren't problems. I think the database would be where most performance issues would surface, not the api server. I'm curious how others will answer your question though because I'm not really sure.
The constraints it imposes pay dividends. Do you write code once and forget it? Or do you often change what your code is doing or how it is structured? Because those changes tend to bring out the most bugs. The type system will really help you with any refactorings. I've done some huge changes to the entire structure of my apps and once it compiles had zero issues. It just worked from first run.
Do you find performance problems in production? How much time is spent on those? If you're in Python/Ruby/Erlang land that can be a huge chunk of your time. A Rust solution is going to be memory and cpu efficient by default. Unless you are really in extreme performance land you are likely not going to need to bother with this at all.
How about problems with deployment or dependency management. The output of rust is an executable more or less self contained. The package management is superb.
Yes, it is faster to develop initially, but after N years and an established product that development speed gets outweighed by other requirements: how easy is it to refactor confidently? How much does it cost to run? How complicated is the deployment? Does it scale?
Not to mention many of the reasons why it's faster to write is because you're punting on handling important issues: can I pass this to that function? Is this a valid state for this variable? Is this data validated?
A language like Rust might bog you down at first because it'll require you to do all of that before you get off the ground. But I'd be willing to bet that, if you factor in the whole cost for N years, it'll eventually turn out cheaper. And if you have experience in it it might not even really slow you down.
Many would say "yeah but you have to survive N years", and maybe I've just been lucky but most of the products I've worked on have been profitable and successful. In all of them we reached the point where it just wasn't as fast to develop anymore, and now the application was very expensive to run, slow to change and filled with nagging bugs.
I have built several APIs with Rust + Axum + Sqlx. I get statically typed SQL queries, rock-solid performance, easy to deploy. Most of these APIs also interface with AWS stuff at some point, and the Rust SDK is just phenomenal to use.
But I also love Rust. I've been writing it for 6 years now, and I am more productive in Rust than any other language (for non-trivial projects). I can write up an API faster in Rust than in Django, because I don't have to spend time digging through configuration files or installing plugins and reading arcane documentation to do what I want. The above stack in Rust is incredibly simple.
I have a few dynamic queries, but for the most what I'm doing is relatively straightforward. I still prefer this over using an ORM, personally.
I found that both the parameterized SQL and ORM/QB have an important role to play due to the partial updates and occasionally query building exercise. None is ideal for every situation.
struct Bar {
id: Uuid,
column_1: i64,
column_2: i64,
column_3: String,
column_4: Uuid,
}
struct UpdateBar {
column_1: Option<i64>,
column_2: Option<i64>,
column_3: Option<String>,
column_4: Option<Uuid>,
}
UPDATE some_table SET
column_1 = COALESCE($1, column_1),
column_2 = COALESCE($2, column_2),
column_3 = COALESCE($3, column_3),
column_4 = COALESCE($4, column_4),
WHERE id = some_id;
Heck people use some incantations of Java for High Frequency Trading even.
Besides, web application bottleneck is usually the database.
Goes to show how benchmark minigames are broken and also that most languages are good enough.