Building Cloud-native applications with Rust - the good, the bad and the ugly
summary
TrueLayer builds a new payments API called pay direct in Rust, using tools like cargo-chef and wiremock and relying on Tokio for async execution; Rust delivers predictable performance, exhaustive enum-based state machines, and explicit Result-based error handling. Pain points are long release builds—up to 15–16 minute compile times—immature cloud-native libraries (teams often contribute ~10 patches), and fragmented async executors, so expect extra work wiring vendor SDKs and standardizing runtimes.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:48Why Rust?
- 2:50Implications of Rewriting a Browser Component in Rust
- 5:42Composition without "surprises"
- 10:05State Machines
- 13:30Predictable performance
- 15:18Compile times
- 17:181. Ecosystem maturity
- 19:13Executor (in)compatibility
- 20:25Intermediate learning resources
- 21:00ZERO TO PRODUCTION IN RUST
related talks
27mThe State of Rust Web Frameworks: Pros, Cons & Use Cases
25mWTF, Rust for Web Development??
46mZen and the Art of Convincing Your Company to Use Rust
43mClosing Keynote
32mBuilding and Maintaining Rust at Scale
59mRust in Production
21mRust - Cargo Cult?
20mMastering Rust on Edge and Cloud — AI/IoT Case Studies