Introducing gRPC-Rust
summary
gRPC-Rust builds on Tonic and adds full gRPC features (load balancing, client health checks) while keeping a pure Rust implementation; Google protobuf codegen calls into Tonic today and the core channel architecture is already functional. Key fixes include security bug: forwarded metadata via ? operator, reduced per-RPC allocations by avoiding owned-message churn, replacing callback lifetimes with direct trait invocations plus a helper for deep load-balancer trees, and better deadline propagation. Beta ships late this year with 1.0 early next year.
AI-written summary · about
chapters (10)
- 0:00Welcome
- 1:27Rust’s popularity
- 3:34Rust’s safety performance
- 5:39Why gRPC Rust
- 6:01gRPC Rust implementation
- 8:53Migrating from Tonic
- 12:23gRPC architecture in Rust
- 17:57Rust design hurdles
- 19:02Project status timeline
- 20:48Q&A
related talks
25mgRPC Rust
16mSafe, Fast, and Scalable: Why gRPC-Rust Should Be Your Next RPC Framework
30mgRPC-Rust: Preview to Stable Release
46mAdopting Rust by gracefully oxidising web applications
31mRustly typed APIs; ... JSON RPC with Rust, Procedural macros and a DSL
04m"Scaling Safety: Rust at Google”
41mCap'n Proto and Rust: Type Systems for Sharing
14mKeynote: Welcome + Opening Remarks