As I’m aiming to launch my product swiftly, I’m exploring various backend technologies to use. A lot of indie developers and startup founders I follow tend to choose more familiar languages such as Node.js, Go, and Java, and they seem to be able to release their MVPs rapidly.
I’m intrigued by Rust as an option, but I’m questioning whether it would be the best fit when the speed of development is crucial. Are there any significant limitations in the Rust ecosystem that could cause delays? Could it be due to a lack of libraries, complex deployment processes, or a challenging learning experience?
For those who have attempted to build a SaaS backend using Rust, did you experience any challenges that led you to consider a more established language instead?
what type of MVP are u aiming for? the complexities can really change the game. I’ve seen devs ace it with Rust on certain backends, while others hit walls with the learning curve when they’re in a hurry. what skills does ur team have? sometimes the “best” tech isn’t the fastest to use.
totally feel you, man! rust’s a bit of a pain to learn at 1st, but once you get the hang of it, the speed and safety are worth it. used actix for my backend and it scaled real well! just gotta push through that curve.
I’ve shipped two MVPs this past year using Rust, so here’s my take. The ecosystem’s gotten pretty solid - Axum and Actix-web work great in production, and you’ve got reliable crates for databases, auth, and APIs. But here’s the catch: Rust’s learning curve and strict compiler will slow you down if your team’s new to it. That said, the upfront pain is worth it. My Rust apps barely need monitoring compared to the Node.js stuff I used to build, and they’re rock solid in production. Docker deployment was smooth too. Bottom line: if your team already knows Rust, go for it. If not, you’ll probably miss your launch date while everyone’s learning.