Someone noted to me recently that using Rust for general purpose microservices like interfacing GraphQL to Postgres makes no sense - it is a system-level language. So far I tend to disagree. I stopped using .Net and are cutting my AWS Lambda code in Rust for a new web project.
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (5)
I believe they dropped the "system-level language" label a while ago. Even their website says.
I've only used rust for fun and learning but I would consider it for anything where safety is a top priority.
I see two use cases where rust can be useful (at least, that is what I have tried so far):
I tend to agree with that for now. But that's mainly because the libraries fro rust aren't always as mature as for example the ones on the JVM. Also partly because of and partly because of Rust, building the same general purpose microservice is faster with other languages.
And also cross cutting concerns like logging and monitoring. Using them as Lambda it's pretty equal to other languages in that respect. But if you run them 'yourself' this becomes more of a concern.
I've mostly use it to practice and learn a statically typed language, with the added benefit of modern tooling and centralized documentation. I particularly like the lack of cruft (relative to C++), and all the nice functional features in Rust like iterators, pattern matching, and closures.
Using it for embedded development and the accompanying server. Pretty cool stuff! I never want to go back to C again.