// the find
Tencent/tquic
A high-performance, lightweight, and cross-platform QUIC library
TQUIC is Tencent's production QUIC library written in Rust, covering the full RFC 9000/9001/9114 stack plus HTTP/3. It targets systems that need a C-compatible QUIC implementation without pulling in a Go runtime or a Node dependency — think embedded, mobile, or high-throughput server infrastructure. If you need something battle-tested at Tencent scale and are comfortable with BoringSSL as a bundled dep, this is worth looking at.
Multipath QUIC support is genuinely rare — most QUIC libraries treat it as a footnote; TQUIC actually implements it with three schedulers (min-RTT, round-robin, redundant). Congestion control is pluggable at runtime: CUBIC, BBR, BBRv3, and COPA are all there, not just mentioned in a roadmap. The fuzz corpus is committed to the repo and CI runs it, which means the protocol parser has actually been hammered — not just unit-tested. The C FFI header (`include/tquic.h`) is first-class, not an afterthought, so you can drop this into a C++ or mobile codebase without writing bindings from scratch.
BoringSSL is vendored as a git submodule, not a swappable TLS backend — if your org has a policy around OpenSSL or rustls, you're blocked before you start. The Rust API is event-callback style, which is correct for this kind of library but requires you to manage state machines manually; there's no async/await surface, so integrating with Tokio means writing your own glue. Documentation is split between English and Chinese and the two versions are not always in sync — some of the advanced config options only appear in the Chinese docs. Star count is modest for a QUIC lib (1.4k), and the adopters list is thin outside Tencent properties, so community troubleshooting resources are sparse compared to quinn or quiche.