Rust in Production with Armin Ronacher

Topics:

Deciding when to use RustConcurrency in RustWhen to create a separate serviceIntroducing Rust at SentryChallenges of writing Python modules in RustCreating Symbolicator, a Rust web service that processes debug filesUsing Actix to create SymbolicatorWhy Rust doesn't need a Django or Rails equivalentConcerns about the stability of the Rust ecosystem and the lack of shared solutionsWhat's missing in the Rust ecosystemWhy developers need better debugging tools

If you're interested in helping Armin build an open source debugging community, reach out to him via e-mail or twitter.

This episode is part of the Rustacean Station feed. Check it out if you're interested in Rust podcasts.

Links:

Armin's TwitterArmin's BlogSentryActixRocketBuilding Sentry: SymbolicatorSymbolicatorSemaphoreMilksnakeWasmerExistential TypesTokio TowerRFC to add Backtraces to standard errorFutureErlang

Show timestamps:

0:37 - What got you interested in Rust?2:19 - Abstraction with good performance in Rust vs Python4:11 - Rust doesn't need asynchronous code5:31 - Building thread safe applications6:26 - What excited you about using Rust?8:20 - Sentry11:02 - Introducing Rust to Sentry13:10 - Anything easier to write in Rust vs Python?16:14 - Writing extensions vs writing services19:22 - Flow of sending a minidump to Symbolicator21:56 - Symbolicator makes sense as a service23:26 - Building a better debugging world24:33 - More things symbolicator does25:27 - What's Milksnake28:04 - Other ways to embed Rust in Python30:08 - Why use Actix for Symbolicator?34:44 - Is it too early to write web applications?37:30 - What would you do differently in hindsight?42:20 - Don't want a Django or Rails43:58 - When to write a web application?47:34 - What do you wish existed in Rust?49:57 - Game backends51:44 - Anything else?53:26 - Why companies aren't using Rust for web development54:23 - Why async/await is not the only blocker for web development56:43 - Resources for web development in Rust58:24 - Wrap Up