quiche
s2n-quic
Our great sponsors
quiche | s2n-quic | |
---|---|---|
26 | 7 | |
8,847 | 1,065 | |
2.2% | 1.7% | |
9.0 | 9.3 | |
7 days ago | about 13 hours ago | |
Rust | Rust | |
BSD 2-clause "Simplified" License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
quiche
-
Nghttp3 1.0.0 – HTTP/3 library written in C
The title of this post puts emphasis on "written in C", making me wonder when this would ever be a desirable feature, given that more secure implementations are available, and can be integrated into old C projects just as easily.
No need to rewrite everything from the ground up: https://github.com/cloudflare/quiche#curl
-
Curl HTTP/3 with quiche discouraged
The issue is dead silent too!
- Best performing quic implementation?
-
Oxy is Cloudflare's Rust-based next generation proxy framework
Even though Oxy is a proprietary project, we try to give back some love to the open-source community without which the project wouldn’t be possible by open-sourcing some of the building blocks such as https://github.com/cloudflare/boring and https://github.com/cloudflare/quiche.
-
How Rust and Wasm power Cloudflare's 1.1.1.1
They’ve been on the Rust train since at least 2019. Just look at projects like quiche, wrangler, and boringtun
-
What is a CDN? How do CDNs work?
It's more like Cloudflare forked nginx a long time ago, and is meanwhile in the very slow (like, decade-long) process of replacing it entirely.
The Cloudflare Workers Runtime, for instance, is built directly around V8; it does not use nginx or any other existing web server stack. Many new features of Cloudflare are in turn built on Workers, and much of the old stack build on nginx is gradually being migrated to Workers. https://workers.dev https://github.com/cloudflare/workerd
In another part of the stack, there is Pingora, another built-from-scratch web server focused on high-performance proxying and caching: https://blog.cloudflare.com/how-we-built-pingora-the-proxy-t...
Even when using nginx, Cloudflare has rewritten or added big chunks of code, such as implementing HTTP/3: https://github.com/cloudflare/quiche And of course there is a ton of business logic written in Lua on top of that nginx base.
Though arguably, Cloudflare's biggest piece of magic is the layer 3 network. It's so magical that people don't even think about it, it just works. Seamlessly balancing traffic across hundreds of locations without even varying IP addresses is, well, not easy.
I could go on... automatic SSL provisioning? DDoS protection? etc. These aren't nginx features.
So while Cloudflare may have gotten started being more-or-less nginx-as-a-service I don't think you can really call it that anymore.
(I'm the tech lead for Cloudflare Workers.)
- Using WebTransport
-
Is it better to learn web development with Python or C?
Ask Cloudflare why they use HTTP/3 and QUIC https://github.com/cloudflare/quiche.
- DNS-over-HTTP/3 in Android
-
The MQTT broker powering Cloudflare's new Pub/Sub product is written in Rust!
Cloudflare has used rust for multiple projects in the past such as their QUIC/HTTP3 implementation Quiche and a WireGuard implementation BoringTun.
s2n-quic
- BoletÃn AWS Open Source, Christmas Edition
-
Kani 0.28.0 has been released!
Yes, the Kani CI time for s2n-quic dropped by more than 25% with Kani 0.28.
- Best performing quic implementation?
-
From Fuzzing to Proof: Using Kani with the Bolero Property-Testing Framework
Packet parsing is a great application for this type of testing. We've used bolero/Kani in a bunch of s2n-quic's codec implementations - example.
- S2n-QUIC (Rust implementation of QUIC)
-
Announcing s2n-quic 1.0
It's definitely a valid question, with there being a lot of great QUIC implementations out there. We do believe, though, s2n-quic has a lot to offer with a high level of security, testing, performance, and features. Given that s2n-quic will eventually be integrated into AWS Services, we ultimately need direct ownership of fundamental libraries like s2n-quic, s2n-tls, etc. to be able to maintain that high level of security and performance for our customers.
What are some alternatives?
quinn - Async-friendly QUIC implementation in Rust
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
tuic - Delicately-TUICed 0-RTT proxy protocol
quic-go - A QUIC implementation in pure Go
neqo - Neqo, an implementation of QUIC in Rust
shadowsocks-rust - A Rust port of shadowsocks
base-drafts - Internet-Drafts that make up the base QUIC specification
rustls - A modern TLS library in Rust
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
rfc8312bis - Revision of RFC8312 "CUBIC for Fast Long-Distance Networks"