coralcdn
quiche
coralcdn | quiche | |
---|---|---|
1 | 26 | |
5 | 8,928 | |
- | 1.3% | |
10.0 | 9.0 | |
almost 10 years ago | 2 days ago | |
PHP | Rust | |
GNU General Public License v3.0 only | BSD 2-clause "Simplified" License |
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.
coralcdn
-
What is a CDN? How do CDNs work?
No mention of Coral CDN:
https://wiki.opensourceecology.org/wiki/Coral_CDN
https://en.wikipedia.org/wiki/Coral_Content_Distribution_Net...
https://github.com/morganestes/coralcdn
Just a few years ago, you could append .nyud.net to any domain and fetch it through the Coral cache instantly. But it's apparently been quietly swept under the rug.
Caching is such a basic thing to do that I'm concerned that the current crop of CDNs will mostly be used for mass surveillance. I also worry that VPNs are used for similar purposes by spy agencies.
IMHO the static web should have been distributed from the start. It should have been https everywhere. We should have kept cookies instead of trying to wedge in security on the frontend with OAuth, which is like a leaky sieve in comparison. We should have had Subresource Integrity (SRI) and been able to load scripts and other sensitive files from these caches fearlessly.
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!
https://github.com/cloudflare/quiche/issues/1115
- 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.
What are some alternatives?
workerd - The JavaScript / Wasm runtime that powers Cloudflare Workers
quinn - Async-friendly QUIC implementation in Rust
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
quic-go - A QUIC implementation in pure Go
shadowsocks-rust - A Rust port of shadowsocks
neqo - Neqo, an implementation of QUIC in Rust
s2n-quic - An implementation of the IETF QUIC protocol
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
quic - quiwi 🥝 - QUIC implementation in Go.
Rust - All Algorithms implemented in Rust
Proxygen - A collection of C++ HTTP libraries including an easy to use HTTP server.
hyperfine - A command-line benchmarking tool