This is an automated archive made by the Lemmit Bot.

The original was posted on /r/rust by /u/Al_Redditor on 2023-08-11 22:49:17.

I was recently able to convince our team to stand up a service using Rust and Axum. It was my first Rust project so it definitely took me a little while to get up to speed, but after learning some Rust basics I was able to TDD a working service that is about 4x faster than a currently struggling Java version.

(This service has to crunch a lot of image bytes so I think garbage collection is the main culprit)

But I digress!

My main point here is that using Rust is such a great developer experience! First of all, there’s a crate called “Axum Test Helper” that made it dead simple to test the endpoints. Then more tests around the core business functions. Then a few more tests around IO errors and edge cases, and the service was done! But working with JavaScript, I’m really used to the next phase which entails lots of optimizations and debugging. But Rust isn’t crashing. It’s not running out of memory. It’s running in an ECS container with 0.5 CPU assigned to it. I’ve run a dozen perf tests and it never tips over.

So now I’m going to have to call it done and move on to another task and I have the sads.

Hopefully you folks can relate.