// the find
cloudwego/volo
Rust RPC framework with high-performance and strong-extensibility for building micro-services.
Volo is ByteDance's production Rust RPC framework supporting Thrift, gRPC, and HTTP, built on top of their own Motore middleware abstraction. It's for teams already committed to Rust who want a full microservices stack with service discovery and load balancing baked in, particularly those migrating from or running alongside ByteDance's Go framework Kitex. If you're writing a small service that just needs gRPC, tonic is probably the easier call.
The RPITIT-based middleware abstraction (Motore) avoids boxing futures at layer boundaries — this is a real performance win that tonic doesn't get because it predates stable AFIT. The code generation story is solid: volo-cli bootstraps projects and manages IDL files, and the generated code handles both Thrift and protobuf from a single tool. The framework is split into genuinely independent crates (volo-thrift, volo-grpc, volo-http) rather than one monolith with feature flags, so you can pull in only what you need. Active maintenance from a team running it in production at scale — the changelog and recent commits show real work, not an abandoned experiment.
volo-http is still 'Work In Progress' per the README, which means if you need HTTP/REST alongside gRPC you're either waiting or stitching in axum yourself. Community support is heavy on Feishu (ByteDance's internal chat tool), which is a friction point for anyone outside that ecosystem — English-language issue responses are slower and the getting-started docs link to Chinese-language guides. The benchmark numbers (350k QPS on 4 cores for Thrift) are self-reported with no independent reproduction scripts you can just run, so treat them as directional. The project's ecosystem (volo-rs org) is small; if you need a middleware that doesn't exist yet, you're writing it.