Rust works out of the box, you can write services, compile, and ship without rethinking your entire stack. But getting the most out of what Rust offers : performance, safety, fine-grained control; requires deliberate system design choices.

This talk focuses on how to design systems that take full advantage of Rust's strengths. How do you structure services so the ownership model becomes a design asset? What architectural patterns unlock the performance Rust is known for? How do you approach memory layout, concurrency, and abstraction boundaries when the language gives you that level of control? And what technical decisions leads to tame the hardess of Async Rust ?

I'll walk through concrete design decisions from shipping Rust in mission-critical infrastructure — what worked, what missed the mark, and what I'd approach differently today.