Quinn Alternatives

quinn reviews and mentions

• Why HTTP/3 is eating the world
  9 projects | news.ycombinator.com | 5 Oct 2023

  Since it lives on top of UDP, I believe all you need is SOCK_DGRAM, right? The rest of QUIC can be in a userspace library ergonomically designed for your programming language e.g. https://github.com/quinn-rs/quinn - and can interoperate with others who have made different choices.

  Alternately, if you need even higher performance, DPDK gives the abstractions you'd need; see e.g. https://dl.acm.org/doi/abs/10.1145/3565477.3569154 on performance characteristics.

• Async rust – are we doing it all wrong?
  9 projects | news.ycombinator.com | 19 Jul 2023

  > Making things thread safe for runtime-agnostic utilities like WebSocket is yet another price we pay for making everything multi-threaded by default. The standard way of doing what I'm doing in my code above would be to spawn one of the loops on a separate background task, which could land on a separate thread, meaning we must do all that synchronization to manage reading and writing to a socket from different threads for no good reason.

  Why so? Libraries like quinn[1] define "no IO" crate to define runtime-agnostic protocol implementation. In this way we won't suffer by forcing ourselves using synchronization primitives.

  Also, IMO it's relatively easy to use Send-bounded future in non-Send(i.o.w. single-threaded) runtime environment, but it's almost impossible to do opposite. Ecosystem users can freely use single threaded async runtime, but ecosystem providers should not. If you want every users to only use single threaded runtime, it's a major loss for the Rust ecosystem.

  Typechecked Send/Sync bounds are one of the holy grails that Rust provides. Albeit it's overkill to use multithreaded async runtimes for most users, we should not abandon them because it opens an opportunity for high-end users who might seek Rust for their high-performance backends.

  [1]: https://github.com/quinn-rs/quinn

• quicssh-rs Rust implementation SSH over Quic proxy tool
  3 projects | /r/rust | 30 Apr 2023

  quicssh-rs is quicssh rust implementation. It is based on quinn and tokio

• The birth of a package manager [written in Rust :)]
  2 projects | /r/rust | 17 Mar 2023

  Regarding Quinn, I had a blast this week resurrecting an old PR. Looking forward to the next!

• Best performing quic implementation?
  4 projects | /r/rust | 5 Mar 2023
• str0m a sans I/O WebRTC library
  3 projects | /r/rust | 18 Dec 2022

  By studying u/djcu/hachyderm.io (and others!) excellent work in Quinn, doing a sans I/O implementation of QUIC https://github.com/quinn-rs/quinn we have a way forward.

• durian - a high-level general purpose client/server networking library
  3 projects | /r/rust_gamedev | 7 Dec 2022

  QUIC isn't web/wasm-compatible because of https://github.com/quinn-rs/quinn/issues/1388, so durian wouldn't either since it's built on top of it.

• FPS server with QUINN?
  3 projects | /r/rust | 29 Oct 2022

  Quinn, as in the implementation of QUIC? https://github.com/quinn-rs/quinn

• I built a Zoom clone 100% IN RUST
  12 projects | /r/rust | 24 Oct 2022

  You are right, I am planning to switch the transport to UDP + quic using the awesome QUINN library, https://github.com/quinn-rs/quinn .

• I write a secure UDP tunnel
  2 projects | /r/rust | 1 Oct 2022

  Hi, I am new to the community, I just started learning rust and created a secure UDP tunnel based on the Quinn library, thanks to Quinn, I didn't need to go into the detail of the QUIC protocol and quickly created a UDP tunnel, and thanks to the BBR congestion control algorithm it uses, the tunnel performs quite well with lousy and long fat network, I didn't do any benchmark, but it performs a lot better (higher throughput with LFN) than most of other TCP tunnel implementations I used before.

• A note from our sponsor - SaaSHub
  www.saashub.com | 12 May 2025

  SaaSHub helps you find the best software and product alternatives Learn more →