A better way of doing Async Rust
summary
Shows a working HTTP server that fetches posts from JSONPlaceholder, adds a cache, and demonstrates how structured concurrency removes the need for pervasive Arc/Mutex and Send+'static clutter — the code compiles and runs without unsafe statics. Explains why Tokio multi-threaded scheduler forces futures to be Send, and how alternatives (single-threaded or thread-per-core) avoid that. Implements non-'static handlers with futures_unordered and a higher-level Morrow scope, and cites Limbo with ~90 contributors and ~10,000 stars as a real-world success.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:10Rust in database projects
- 1:10Limbo project overview
- 1:49Example application
- 2:50Basic implementation
- 4:00Caching and lifetimes
- 7:18Structured concurrency
- 10:05Understanding Send/Sync
- 13:12Optimizing async code
- 15:05Conclusion and Q&A
related talks
29mAsychronous programming in Rust
46mA Tale of Two Asyncs
02h 02mCloud Native Rust Workshop: Let's go parallel with Rust
56mThe RUST Language for High‑Load Network Services — Quick Start
32mTechniques for writing concurrent applications with asynchronous I/O
30mDay2 02 Sean Klein
32mLet's build an async runtime together
20mIt's Critical: Concurrent programming as a sane programming model